Bug #72560 Mysql Workbench crashs when starting; Windows 7 Professional
Submitted: 7 May 2014 14:42 Modified: 13 Jul 2014 10:38
Reporter: André Inocenti Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.1.4 CE OS:Windows (7 Professional)
Assigned to: CPU Architecture:Any
Tags: crashs, reinstall

[7 May 2014 14:42] André Inocenti
Description:
Hi, my Workbench started to crashs when I open it.

I tried reinstall it many times. I also deleted the dir AppData/Roaming/Mysql/Workbench.

I also cleared my registers and temporary files with Advanced System Care.

PS.: When I reinstall Workbench it opens and works fine for the first time only. So when I close it, it stops to work. It crashs when I try to initiate it again.

How to repeat:
It Happens every time i start it. But when I reinstall the software it opens for the first time only. After that starts to crash.
[7 May 2014 14:46] MySQL Verification Team
Which exactly version are you using 6.1.4?. Thanks.
[7 May 2014 14:47] André Inocenti
Yes. The version is 6.1.4
[7 May 2014 20:58] MySQL Verification Team
Do you have checked Preferences->General->Automatically reopen previous model at start ?. Thanks.
[7 May 2014 21:01] André Inocenti
It is unchecked. 

Can it be a problem in my windows? Maybe same DLL with problem?

The weird thing is that it opens only the very first time I reinstall it, after that only crashs.

Thanks.
[15 May 2014 22:55] Alfredo Kojima
Please upload the wb.log file. Also what error is printed when it crashes?
[13 Jun 2014 10:38] MySQL Verification Team
Thank you for the report.
WB version 6.1.4 is old and many bugs were fixed since. Please upgrade
to current version 6.1.6, try with it and inform us if problem still
exists.

http://dev.mysql.com/downloads/workbench/
[14 Jul 2014 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".