Bug #52589 Autolayout Unhandled Exception
Submitted: 5 Apr 2010 3:34 Modified: 6 Jul 2010 6:03
Reporter: Charles Whipple Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.17 OSS Beta, 5.2.19 OS:Windows (Windows 7)
Assigned to: CPU Architecture:Any
Tags: Autolayout in ERR diagramThrows Error

[5 Apr 2010 3:34] Charles Whipple
Description:
If you click Arrange->Autolayout inside an EER designer, it blows up.  I have a very complicated DB design with foreign keys and junction tables everywhere, so I'm uncertain if its due to the complexity of the DB or if its an error that would be present on every design.  

How to repeat:
Click Arrange->Autolayout

Suggested fix:
Fix the Autolayout functionality and Handle the exception.  There is obviously not a try-catch block inside the event handler for the menu item.
[5 Apr 2010 5:36] Valeriy Kravchuk
Can you send your problematic model? This crash does not happen with my models. Also, please, send the results from Help > System Info menu item.
[5 Apr 2010 6:35] Charles Whipple
I cannot give you the model.  The max file size for uploads is 500kb and the .png produced is 900+kb.  The DB script is nearly 2 megs(without data).  Also, due to the line that says anything uploaded becomes property of Sun, I'm not certain that I would like to do that.  This DB is proprietary.  If you cannot reproduce the error, i would suggest insuring that there is a try-catch in the event handler for the menu item and in the next release I'll send you the stack trace.
[5 Apr 2010 11:32] MySQL Verification Team
Thank you for the feedback. i couldn't repeat with the example model Sakila too, please provide the output of Help -> System Info like below for my machine:

MySQL Workbench OSS for Windows version 5.2.17

Cairo Version: 1.8.8

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

OpenGL Driver Version: 3.2.9232

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

CPU: 4x AMD Phenom(tm) 9650 Quad-Core Processor, 7.8 GiB RAM

Video adapter info:

Adapter type: 

Chip Type: ATI display adapter (0x9610)

BIOS String: BK-ATI VER010.087.000.001.000000

Video Memory: 262144 KB

Also describe with more details your model and if suspect condition before to click the Autolayout. Thanks in advance.
[7 Apr 2010 0:15] Charles Whipple
Sorry for the delay.  Here is the system information: 

MySQL Workbench OSS for Windows version 5.2.17

Cairo Version: 1.8.8

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

OpenGL Driver Version: 2.1.8787

OS: Microsoft Windows 7 Home Premium Edition (build 7600), 64-bit

CPU: 8x Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz, 4.0 GiB RAM

Video adapter info:

Adapter type: ATI Radeon HD 4800 Series

Chip Type: ATI display adapter (0x9442)

BIOS String: 113-B50107-100

Video Memory: 524288 KB
[7 Apr 2010 0:28] Charles Whipple
Also, I can just start MySQL, go directly to the EER modeling, click the menu item, and the error happens.  This would lead me to believe that the error is with the model.  Perhaps its due to the complexity or perhaps a relationship that the Workbench does not know how to handle.  The model currently has 55 tables in the design.  Each table has 1-7 foreign keys in it.
[18 Apr 2010 17:32] MySQL Verification Team
Thank you for the feedback. Could yoiu please try version 5.2.19 if the issue continues please provide the file of the model project? (private if you wish). Thanks in advance.
[24 Apr 2010 2:52] Charles Whipple
First thanks for putting my mouse wheel scroll back into the Data Modeling.  I thought my head was going to explode.  

The bug is still in present in the Arrange-Auto Layout. It seems as though no error handling has been implemented either.  It crashes the program with no attempt to recover. I actually tried to debug the problem.  At one point I launched VS 2008 because I was prompted with the option to debug, but it said no frames were loaded.

Attached you will find a dump file.  I hope this helps. 

Here is the Sys Information in case you want it again (It appears as though a bug has crept into the the formatting of the sys info): 
MySQL Workbench SE for Windows version 5.2.19
Cairo Version: 1.8.8
Rendering Mode: OpenGL is available on this system, so OpenGL is used for rendering.
OpenGL Driver Version: 2.1.8787
OS: Microsoft Windows 7 Home Premium Edition (build 7600), 64-bit
CPU: 8x Intel(R) Core(TM) i7 CPU         920  @ 2.67GHz	(�r	��r	��r	�
@�Ȳ�
, 4.0 GiB RAM
Video adapter info:
Adapter type: ATI Radeon HD 4800 Series
Chip Type: ATI display adapter (0x9442)
BIOS String: 113-B50107-100
Video Memory: 524288 KB
[26 Apr 2010 8:25] Sveta Smirnova
Thank you for the SQL.

I got message: "OpenGL error: invalid value" trying to import it.
[26 Apr 2010 8:26] Sveta Smirnova
Same error when "Arrange->Autolayout", so bug can be considered verified.
[28 Apr 2010 14:51] Alfredo Kojima
I cannot repeat it in Windows 7. Please take a screenshot of the exception dialog and upload so we can at least see what is it about and try tracking from there.
[29 Apr 2010 14:04] Alfredo Kojima
Sveta,

The crash you saw is probably the same as this one:
http://bugs.mysql.com/bug.php?id=52840

Charles,
Can you confirm whether the exception you get is the same as the above one and Sveta also describes?
[29 Apr 2010 14:43] Charles Whipple
I do not believe this is the same error.  I never see anything as described in the bug 52840.  I can scroll around just fine in the model.  I have never seen an error with a message when performing attempting to perform the autolayout.  It simply crashes.  If i got an error message that said something about an Open GL error, I may be inclined to believe this is the same bug; however, I get no messagebox and the whole workbench hits a fatal crash.
[8 Jun 2010 14:30] Alfredo Kojima
Please check with latest version, a similar bug has been fixed recently.
[12 Jun 2010 6:34] Charles Whipple
Still an issue.
[6 Jul 2010 6:03] Sveta Smirnova
Not repeatable for me with version 5.2.25. Please upgrade.