Bug #52780 MySQlLWorkbench freezes on start-up when screen-saver activates
Submitted: 13 Apr 2010 10:51 Modified: 27 Apr 2010 9:08
Reporter: Kai Sautter (Basic Quality Contributor) Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.19 OS:Windows (XP)
Assigned to: CPU Architecture:Any
Tags: qc

[13 Apr 2010 10:51] Kai Sautter
Description:
MySQL Workbench does not start-up correctly, if the Windows sceensaver activates (or is activated by the user) after MySQLWorkbench.exe has been called. The result is a screen that shows the schemes of the three list boxes on the entry screen on top of the Windows Desktop background. The application window can be activated, yet this does not change window content. The application keeps showing the busy cursor (hourglass mouse pointer).

If the MySQL Workbench application window is covered another application window and then uncovered again (by minimizing the other application), The screen will still show most parts of the window pane of the other application. This indicates that MySQL Workbench has frozen.

The Windows window list (Alt-Tab) shows two windows icons (MySQL Workbench main window and MySQL Workbench splash screen).

If the screen-saver is forced to activate prior to the splash screen to appear, the application will start in minimized mode. Once the application window is activated, it will show the same behavior.

Reproduction was possible with the following version:

5.1.18 (Build 4456)
5.2.16 (Build 5249)
5.2.17 (Build 5565)

No other version have been tested.

How to repeat:
1) Call MySQLWorkbench.exe
2) Wait for the splash screen to appear
3) Press the Windows key + L to activate the screen saver
4) Wait at least for the time it would normally take Workbench to start up
5) Deactivate the screen-saver

The behavior was reproducible on a machine with a password protected screen-saver. No tests have been performed without password protection.
[21 Apr 2010 17:45] Johannes Taxacher
can't repeat on my win7 box (although on vista/7 win+L locks the screen instead of activating the screensaver)
[22 Apr 2010 9:27] Kai Sautter
Thank you for checking against other Windows versions. Johannes Taxacher correctly points to an error in my bug description; the key combination Windows + L indeed calls the routine to lock the PC, not the to activate the screen saver (also on XP).

Though, this limits the bug to specific user action, unfortunately it does not change the probability of occurrence.

I made another test with MySQL Workbench Version 5.2.19 on Windows XP and was able to reproduce the bug. The specific version of the operating system is XP Professional with Service Pack 3 Build 2600 (i.e. Version 5.1.2600).
[26 Apr 2010 9:02] Sveta Smirnova
Thank you for the feedback.

Problem is repeatable on Vista for me, but with different screenshot: WB opened, stalled and no control can be accessed, I have to kill WB using Ctrl+Alt+Del, then restart to get it working. I used Windows Key + L to lock screen. Screenshot will be uploaded shortly.
[26 Apr 2010 9:04] Sveta Smirnova
Screenshot

Attachment: bug52780.jpg (image/jpeg, text), 215.32 KiB.

[26 Apr 2010 14:07] Mike Lischke
Fixed in repository.
[26 Apr 2010 21:53] Johannes Taxacher
fix confirmed in repository
[27 Apr 2010 9:08] Tony Bedford
An entry has been added to the 5.2.20 changelog:

While MySQL Workbench was starting up, if the Windows screensaver activated, this led to unpredictable behavior of MySQL Workbench. For example, the application could freeze, fail to redraw its main window, or display artifacts. On other occasions the application was not able to accept keyboard input, and had to be terminated using the Task Manager.