Bug #52829 | happened when i pressed zoom in/out in the eer diagram | ||
---|---|---|---|
Submitted: | 14 Apr 2010 15:37 | Modified: | 29 Apr 2010 16:29 |
Reporter: | morten hundevad | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench: Modeling | Severity: | S3 (Non-critical) |
Version: | 5.2.18 rev 5625 | OS: | Windows |
Assigned to: | Mike Lischke | CPU Architecture: | Any |
[14 Apr 2010 15:37]
morten hundevad
[14 Apr 2010 15:46]
Valeriy Kravchuk
Thank you for the problem report. What exact version of MySQL Workbench, 5.2.x, do you use? Send the results from Help > System Info menu item also.
[14 Apr 2010 16:33]
morten hundevad
sorry i forgot to add the version =( i know how it is as i work with programing/support my self as well 5.2.18 rev 5625 ------------- system info ------------- SQL Script Export CompletedMySQL Workbench SE for Windows version 5.2.18 Cairo Version: 1.8.8 Rendering Mode: OpenGL is not available on this system, INTERNAL ERROR, contact the authors. OpenGL Driver Version: Not Detected OS: Microsoft Windows XP Professional Service Pack 3 (build 2600) CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz, 2.5 GiB RAM Video adapter info: Adapter type: Intel(R) 82945G Express Chipset Family Chip Type: Intel(R) 82945G Express Chipset Family BIOS String: Intel Video BIOS Video Memory: 131072 KB --------------------------------------- hope it helps
[14 Apr 2010 17:59]
MySQL Verification Team
Thank you for the feedback. I couldn't repeat using the Sakila model file project, that happens on your side all the time or in random way?. Could you please provide your model file to test it on our side. Thanks in advance.
[14 Apr 2010 18:18]
morten hundevad
just realize that the workbeanch also make my pc crash 2 times now. 1# when i opened the program for the first time (thought it was something else at first) #2 when i tried to open the project form the .mwb file two different error messages, the first is the BSOD (i think) that cause the reboot: BCCode : 1000008e BCP1 : C0000005 BCP2 : BF93A34E BCP3 : A89998C0 BCP4 : 00000000 OSVer : 5_1_2600 SP : 3_0 Product : 256_1 2nd: unknown ? to be excact because i was trying to write this and open the app at the same time. so not 100% sure this has anything to do with the BSOD: EventType : clr20r3 P1 : mysqlworkbench.exe P2 : 5.2.18.5625 P3 : 4bc42a47 P4 : mysqlcsutilities P5 : 1.0.0.0 P6 : 4bc42682 P7 : 59 P8 : 26 P9 : system.exception NOTE: i am not sure if any of this is related so i am posting it here all tho i suspect the reboot problem is different from the zoom problem.
[14 Apr 2010 18:19]
morten hundevad
from BSOD
Attachment: sysdata.xml (text/xml), 0 bytes.
[14 Apr 2010 18:19]
morten hundevad
not sure if you can use this or it is only microsoft
Attachment: Mini041410-02.dmp (application/octet-stream, text), 88.00 KiB.
[14 Apr 2010 18:30]
MySQL Verification Team
Thank you for the feedback. I got an error while trying to open your model file even isn't the same error reported .
[21 Apr 2010 15:21]
Johannes Taxacher
Morten, could you try to launch Workbench using the -swrendering parameter and see if it still goes down? (looks like theres an opanGL problem on some intel boards/drivers ... thanks in advance
[21 Apr 2010 15:31]
morten hundevad
like this ? target: "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS\MySQLWorkbench.exe -swrendering"
[21 Apr 2010 15:33]
morten hundevad
tried target: "C:\Program Files\MySQL\MySQL Workbench 5.2 OSS\MySQLWorkbench.exe" -swrendering no error message come up now
[28 Apr 2010 9:38]
Mike Lischke
Fixed in repository.
[28 Apr 2010 11:02]
morten hundevad
great =)
[29 Apr 2010 15:05]
Mike Lischke
Bug #53214 has been marked as a duplicate of this one.
[29 Apr 2010 15:08]
Johannes Taxacher
fix confirmed in repository
[29 Apr 2010 16:29]
Tony Bedford
An entry has been added to the 5.2.21 changelog: When zooming in and out of the EER Diagram view, MySQL Workbench generated an unknown error.
[9 Jun 2010 9:43]
Sveta Smirnova
Users report same problem in 5.2.22: see bug #54210
[21 Jul 2010 10:30]
Roel Van de Paar
Even though this bug contains a fix, (at least some part of?) the issue is still there. See bug #55390 comment [21 Jul 12:29] for info.