Bug #70920 Mysql Workbench repeatdly crashes at startup
Submitted: 15 Nov 2013 11:12 Modified: 5 Dec 2013 19:33
Reporter: Aurélien Panhaleux Email Updates:
Status: Closed Impact on me:
Category:MySQL Workbench Severity:S1 (Critical)
Version:6.0 CE OS:Windows (Windows 8.1)
Assigned to: CPU Architecture:Any
Tags: 6.0, annoying, crash, startup, workbench

[15 Nov 2013 11:12] Aurélien Panhaleux
Hello to all Mysql community,

Since yesterday I can't use anymore Mysql workbench because he crashes everytime at startup. See the error message below :

"Mysql workbench has encoutered a problem
We are sorry for the inconvenience but an unexpected exception has been raised by one of the MySQL Workbench modules. In order to fix this issue we would kindly ask you to file a bug report. You can do that by pressing the [Report Bug] button below. 

Please make sure to include a detailed description of your actions that lead to this problem.

Thanks a lot for taking the time to help us improve MySQL Workbench!

The MySQL Workbench Team"

I was using Mysql workbench for like 1 month now and everything was fine, except rares crashes.
I work on a database that has around 150 tables, but with small amount of datas on each, so a dump size is around 5MB not more.

The only thing I remember that happened before that series of crashes is me trying to save one mysql open script tabs, and getting error messages like "error : string too long", but the tab was saved anyway. When trying to open this tab, I've had another error message that I can't really remember but it was a matter of size again, but the datas was shown anyway.
The crash happened at one more save attempt on this bugged tab, then it was impossible to start Mysql workbench normally again.

Here is the detail from Windows ^.^ (french version)

  Nom d’événement de problème:	APPCRASH
  Nom de l’application:	MySQLWorkbench.exe
  Version de l’application:
  Horodatage de l’application:	5220ca31
  Nom du module par défaut:	KERNELBASE.dll
  Version du module par défaut:	6.3.9600.16408
  Horodateur du module par défaut:	523d4548
  Code de l’exception:	e06d7363
  Décalage de l’exception:	00012eec
  Version du système:	6.3.9600.
  Identificateur de paramètres régionaux:	1036
  Information supplémentaire n° 1:	5861
  Information supplémentaire n° 2:	5861822e1919d7c014bbb064c64908b2
  Information supplémentaire n° 3:	01d7
  Information supplémentaire n° 4:	01d7340064827245f2249cd1f1a7c264

Thanks by advance for your help ! Hope this could help other users too.

How to repeat:
I don't know =)

Suggested fix:
I don't know either
[18 Nov 2013 20:12] MySQL Verification Team
Please check for duplicate with http://bugs.mysql.com/bug.php?id=70262 (check the workaround)also upgrade to 6.0.8. Thanks.
[19 Nov 2013 11:15] Aurélien Panhaleux
Thank for the redirection.

By deleting the script file who had a size defined at 0kb I managed to start again Mysql Workbench.
Could you tell me what should I do to prevent this bug from happening again in the future ?

Also please note that the check for upgrades in Mysql intaller does not suggest me to upgrade to Workbench 6.0.8 ;)

Thanks by advance
[5 Dec 2013 19:33] Alfredo Kojima
You can download WB 6.0.8 directly from dev.mysql.com/downloads