Bug #50856 Workbench triggers Windows "crash" report
Submitted: 2 Feb 2010 20:57 Modified: 3 Mar 2010 8:51
Reporter: Daniel Katz Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.15.5053 OS:Windows (Windows 7)
Assigned to: CPU Architecture:Any
Tags: Microsoft Crash

[2 Feb 2010 20:57] Daniel Katz 
Description:
When closing the MySQL Workbench, a microsoft crash window is triggered saying that 

"MySQL Workbench has stopped working."

Although it looks like it's the ATI dll seems to be reporting the error, this is the only program that throws a fault.

How to repeat:
Open workbench.  Close workbench.

or

Open workbench.. do anything...  close workbench..

Additional information:

Problem signature:
  Problem Event Name:	BEX
  Application Name:	MySQLWorkbench.exe
  Application Version:	5.2.15.5053
  Application Timestamp:	4b609c0e
  Fault Module Name:	atioglxx.dll_unloaded
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	4a8a0dde
  Exception Offset:	69830910
  Exception Code:	c0000005
  Exception Data:	00000008
  OS Version:	6.1.7600.2.0.0.256.48
  Locale ID:	1033
  Additional Information 1:	0a9e
  Additional Information 2:	0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:	0a9e
  Additional Information 4:	0a9e372d3b4ad19135b953a78882e789

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt
[2 Feb 2010 20:58] Daniel Katz 
It's not "serious" .. but it is a crash.
[3 Feb 2010 8:51] Johannes Taxacher 
Hi Daniel,

what gfx card are you using and what driver version (i guess some version of the catalyst driver suite).
Does that happen every time you close WB or just in some situations?
[4 Mar 2010 0: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".