Bug #26378 Export Model as Image
Submitted: 14 Feb 2007 19:25 Modified: 15 Feb 2007 9:38
Reporter: Allan Bogh Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Preview Severity:S2 (Serious)
Version:1.1.9a OS:Windows (XP SP2)
Assigned to: CPU Architecture:Any

[14 Feb 2007 19:25] Allan Bogh
Description:
Export Model as Image reports an error of "Access violation at address 6921219D in module 'atioglxx.dll'. Read of address 00000120."

I have an ATI Radeon Express 200M. This seems to be a problem with how the image exporter is accessing the video card - using a non-standard protocol. Another bug report mentioned this exact problem but no solution was given, it was verified however.

After attempting the Export as Image command the program continues to work, but won't print and also uses 99% of the CPU. The user has just a few seconds to kill the task in the task manager before it slows everything down. Closing the program from the window does not end the process.

This seems to occur if the workbench has tables in it. On a clean workbench the images are created successfully. It has no dependency on reverse-engineered DBs, only if there is at least one table on the workbench, even if the table has the default values.

How to repeat:
Use a computer with a ATI graphics card (preferably ATI Radeon Express 200M) and XP SP2.

Drop one table onto a new workbench or reverse engineer a DB.

Click File - Export - Model as Image

Choose a location and export image.

Notice in the status menu (at the bottom of the screen) an access violation, which will display for several seconds then disappear.

Close the program.

Open the task manager within a few seconds (CTRL-ALT-Delete).

Notice the CPU load on Mysql Workbench, end the Mysql Workbench process to reduce the load and save your computer.

Suggested fix:
Use a standardized image exporter.

Also, ensure the view only exports the image with tables in it, not the entire canvas.
[15 Feb 2007 9:38] Sveta Smirnova
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely
to be the same. Because of this, we hope you add your comments to the original bug instead.

Thank you for your interest in MySQL.

Duplicate of bug #21773