MySQL Bugs: #58403: Workbench crashes within 3 to 15 minutes

Bug #58403	Workbench crashes within 3 to 15 minutes
Submitted:	22 Nov 2010 21:23	Modified:	25 Jan 2011 9:41
Reporter:	Peter Kniaz	Email Updates:
Status:	Can't repeat	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.29CE Rev6756	OS:	Windows
Assigned to:		CPU Architecture:	Any
Tags:	Workbench Administration Crash

Description:
Everytime I get into Administration it runs fine and then after 3 to 30 minutes it crashes or becomes unresponsive while I'm not using it.  Usually the following Microsoft Windows message is displayed: "A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available."
We are connecting to HP-UX, mysql server: 5.0.77-log.  
Workbench is running on Vista, version 5.2.29CE Rev 6756.  
As far as I know it exhibited the same behaviour in the previous version of Workbench.  
WB SQL editor works great.  Also, the old Mysql Administrator that came with Query Browser works fine.

How to repeat:
Get into WB Administrator and spend 3 to 30 minutes doing other things (e.g., queries in WB SQL Editor, or something in Excel, or whatever.

Suggested fix:
NA

Could you please provide the output of Help->System Info and try version 5.2.30. Thanks in advance.

Help->system_info output
<type 'instance'>

MySQL Workbench CE for Windows version 5.2.29

Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE

Cairo Version: 1.8.8

Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.

OpenGL Driver Version: 1.5.0 - Build 7.14.10.1253

OS: Microsoft Windows Vista Business Edition Service Pack 2 (build 6002), 32-bit

CPU: 2x Intel(R) Core(TM)2 Duo CPU     T7300  @ 2.00GHz, 3.5 GiB RAM

Video adapter info:

Adapter type: Mobile Intel(R) 965 Express Chipset Family

Chip Type: Mobile Intel(R) 965 Express Chipset Family

BIOS String: Intel Video BIOS

Video Memory: 458752 KB

Current user language: English (United States)

Please, check if this ever happens when you try to administer local server.

I was waiting for 30+ minutes, but no problem happened when I was connected with WB 5.2.30 to local 5.0.91 on Windows XP.

Also, when crash happens next time, please, right click on any part of error dialog box not containing text, click on "Copy stack trace to clipboard" in the context menu and upload stack trace to this report.

Help->system_info output
<type 'instance'>

MySQL Workbench CE for Windows version 5.2.29

Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE

Cairo Version: 1.8.8

Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.

OpenGL Driver Version: 1.5.0 - Build 7.14.10.1253

OS: Microsoft Windows Vista Business Edition Service Pack 2 (build 6002), 32-bit

CPU: 2x Intel(R) Core(TM)2 Duo CPU     T7300  @ 2.00GHz, 3.5 GiB RAM

Video adapter info:

Adapter type: Mobile Intel(R) 965 Express Chipset Family

Chip Type: Mobile Intel(R) 965 Express Chipset Family

BIOS String: Intel Video BIOS

Video Memory: 458752 KB

Current user language: English (United States)

OK -- version 5.2.30 is better.  Instead of crashing, now the only thing that seems to happen after about 15 minutes is that the little graphs at the top of the screen go blank and indicate "No Data".  (They seem to work fine for the first 15 minutes or so.)
(Sorry about the multiple Sys Info's -- my browser wasn't responding -- so I kept hitting submit.)

Could you please provide a step by step instruction about the last issue commented? and also a screen-shot?. Thanks in advance.

I get into Workbench Administration
The little graphs at the top start filling with information
I minimize the window of Workbench Administration and start doing other things
I open the window back up in about 15 minutes and now the graphs show "no data".

Please try version 5.2.31. Thanks in advance.

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".

At 5.2.31 I no longer see these problems.  Thanks.

Not repeatable with 5.2.31.