Bug #54210 | Resized window at unexpected error comes up | ||
---|---|---|---|
Submitted: | 3 Jun 2010 16:23 | Modified: | 21 Jul 2010 10:14 |
Reporter: | Sha Sto | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 5.2.22 OSS RC r 6091 | OS: | Windows |
Assigned to: | CPU Architecture: | Any | |
Tags: | crash, resized, unexpected, zoom |
[3 Jun 2010 16:23]
Sha Sto
[3 Jun 2010 16:25]
Sha Sto
Screenprint of report window
Attachment: Untitled.jpg (image/jpeg, text), 328.44 KiB.
[3 Jun 2010 17:30]
MySQL Verification Team
Thank you for the bug report. I couldn't repeat on Vista Home Premium 64-bit, could you please provide the output of Help->System Info and the model project file which cause the behavior reported?. Thanks in advance.
[4 Jun 2010 8:35]
Sha Sto
Here we go: MySQL Workbench OSS for Windows version 5.2.22 Cairo Version: 1.8.8 Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering. OpenGL Driver Version: 2.1.7659 Release OS: Microsoft Windows Vista Home Premium Edition Service Pack 1 (build 6001), 32-bit CPU: 2x AMD Athlon(tm) 64 X2 Dual Core Processor 4400+, 2.0 GiB RAM Video adapter info: Adapter type: Radeon X1300/X1550 Series Chip Type: ATI Radeon Graphics Processor (0x7183) BIOS String: 113-A67626-103 Video Memory: 262144 KB Just crashed on me again this morning, when I used the mouse scroll on the main window.
[8 Jun 2010 23:41]
MySQL Verification Team
See bug: http://bugs.mysql.com/bug.php?id=54351.
[9 Jun 2010 9:19]
Valeriy Kravchuk
I also can not repeat it on 32-bit XP SP3. Looks like this is a videocard-specific problem.
[17 Jun 2010 14:52]
Mike Lischke
Sha, it appears nobody of us can reproduce this problem, so the assumption from Valeryi it is a graphics board or driver problem seems plausible. To verify that please start WB with the command line switch -swrendering. It will be much slower when painting (using GDI rendering instead OpenGL) but so we can see if that is really the culprit.
[17 Jun 2010 15:14]
Mike Lischke
Sha, in addition to that, when you get the exception dialog you can right click on any free space on it to get a context menu that allows to copy the stack trace to the clipboard. Please copy that here so we can take a look.
[19 Jun 2010 19:27]
Sha Sto
Hi, I downloaded the latest version (5.1.18a) at work & it hasn't crashed since. Thanks anyway guys.
[19 Jun 2010 21:19]
Mike Lischke
Closed since reporter said the problem is gone now.
[21 Jul 2010 10:14]
Roel Van de Paar
I was able to crash workbench using the mwb previously provided. This is a duplicate of bug #55390 - will add backtrace in a private comment there.