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: | |
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
[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.