Bug #57541 Application Crash
Submitted: 18 Oct 2010 21:21 Modified: 27 Nov 2010 12:02
Reporter: Michael Rincones Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.29 OS:Windows
Assigned to: CPU Architecture:Any
Tags: appcrash

[18 Oct 2010 21:21] Michael Rincones 
Description:
At different times the application will just crash. Sometimes I'll be activly using it other times I'll be working on something else (another application) and then all of the sudden it crashes in the background. For the most part I'm connected to a remote mysql server, not working on anything locally. 

Description:
  Stopped working

Problem signature:
  Problem Event Name:	APPCRASH
  Application Name:	MySQLWorkbench.exe
  Application Version:	5.2.29.6756
  Application Timestamp:	4cb2cc03
  Fault Module Name:	LIBMYSQL.dll
  Fault Module Version:	0.0.0.0
  Fault Module Timestamp:	4b8c387c
  Exception Code:	c0000005
  Exception Offset:	0003794c
  OS Version:	6.1.7600.2.0.0.256.48
  Locale ID:	1033

::::From Event Viewer::::
Faulting application name: MySQLWorkbench.exe, version: 5.2.29.6756, time stamp: 0x4cb2cc03
Faulting module name: LIBMYSQL.dll, version: 0.0.0.0, time stamp: 0x4b8c387c
Exception code: 0xc0000005
Fault offset: 0x0003794c
Faulting process id: 0x153c
Faulting application start time: 0x01cb6f0236e9924d
Faulting application path: C:\Program Files\MySQL\MySQL Workbench 5.2 CE\MySQLWorkbench.exe
Faulting module path: C:\Program Files\MySQL\MySQL Workbench 5.2 CE\LIBMYSQL.dll
Report Id: 903ae7dd-daf9-11df-937a-005056c00008

How to repeat:
no clear steps to repeat it. it just happens randomly, but i did notice that this started happening after the lastest update. Before then I couldn't remember it crashing.
[27 Oct 2010 12:02] Johannes Taxacher 
Hi Michael,
when these crashes accur, does the application completely go down, or do you see a "MySQL Workbench Unexpected Error"-diallog? if you see that dialog, could you please right-click somewhere inside the dialog and select "copy stack trace to clipbrd" and the add the copied information to this report?
thanks in advance
[28 Nov 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".