Bug #66562 MySql Workbench crashes on start
Submitted: 28 Aug 2012 2:46 Modified: 13 Oct 2012 15:39
Reporter: Wendy Yu Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Workbench Severity:S1 (Critical)
Version: OS:Windows (7 professional x64 SP1)
Assigned to: CPU Architecture:Any
Tags: 64bit, crash, regression, startup, win7, workbench

[28 Aug 2012 2:46] Wendy Yu
It worked yesterday.
After some application crashed, I restarted my computer. 
Then MySql Workbench crashes on start.
I remove and reinstall mysqlworkbench several times.

And repair others:
    Microsoft .NET Framework 4 Client Profile
    Microsoft Visual C++ 2010 Redistributable Package (x86)

It doesn't work.

I'm not sure where the problem is.
Thanks for any help.


Here is description:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="Application Error" /> 
  <EventID Qualifiers="0">1000</EventID> 
  <TimeCreated SystemTime="2012-08-28T02:02:23.000000000Z" /> 
  <Security /> 
- <EventData>
  <Data>C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\MySQLWorkbench.exe</Data> 
  <Data>C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE\grt.dll</Data> 

And always accompany with:

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name=".NET Runtime" /> 
  <EventID Qualifiers="0">1026</EventID> 
  <TimeCreated SystemTime="2012-08-28T02:02:21.000000000Z" /> 
  <Security /> 
- <EventData>
  <Data>應用程式: MySQLWorkbench.exe Framework 版本: v4.0.30319 描述: 處理序已終止,因為有未處理的例外狀況。例外狀況資訊: 例外狀況代碼 c0000005,例外狀況位址 05BA4D43 堆疊:</Data> 

How to repeat:
Suddenly happened on my computer yesterday, It worked ok before.
I don't know how to repeat on other computer.
[28 Aug 2012 5:43] Wendy Yu
After removing 5.2.42, I try to install older versions which downloaded from from http://dev.mysql.com/downloads/workbench/1.0.html and older work, 
but not work.
[13 Sep 2012 15:39] MySQL Verification Team
Please try version 5.2.43 . Thanks.
[14 Oct 2012 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".