MySQL Bugs: #51683: "Unknown Exception caught in Canvas.h"

Bug #51683	"Unknown Exception caught in Canvas.h"
Submitted:	3 Mar 2010 9:56	Modified:	16 May 2010 13:39
Reporter:	Arnaud Jacquemin	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.16 OSS beta	OS:	Windows (Vista without Aero)
Assigned to:		CPU Architecture:	Any

Description:
During the reverse engineering process, at the "Reverse Engineer" step, a dialog pops-up saying : 

Unknown Exception caught in c:\documents and settings\mysqldev\build\mysql-workbench-oss-5.2.16\backend\windows\wbpublic.wr\Canvas.h at line 151

Version info:
You are currently using MySQL Workbench 5.2.16 OSS, Revision 5249

System info:
MySQL Workbench OSS for Windows version 5.2.16
Cairo Version: 1.8.8
Rendering Mode: OpenGL requested (create a diagram to confirm)
OpenGL Driver Version: 2.0.6465 Release
OS: Microsoft Windows Vista Home Premium Edition (build 6000), 32-bit
CPU: 2x AMD Athlon(tm) 64 X2 Dual Core Processor 4400+, 1.8 GiB RAM
Video adapter info:
Adapter type: 
Chip Type: ATI Radeon X1200 Series (0x791E)
BIOS String: BK-ATI VER011.000.000.000.024637
Video Memory: 262144 KB

How to repeat:
Using the "Create EER Model from Existing Database" functionality

Screenshot

Attachment: exception.png (image/png, text), 95.38 KiB.

Does this happen on different/every schema you are trying to reverse engineer or does it seem to appear schema/object specific? could you maybe add a dump of the schema to this report (you can mark uploaded files as private if you don't them to be publicly available).
thanks in advance

This happens on every schema. In fact I do not have to reverse engineer : the simplest way to repeat this bug on my computer is
- Create new EER model
- Add diagram
and then the "Unknown Exception" dialog appears.
There is a strange graphic behavior too : the window doesn't seem to repaint anymore.

Please attache the stack trace.

http://bugs.mysql.com/how-to-report.php

"If the product is crashing, include a backtrace. Instructions for doing this can be found here. "

http://dev.mysql.com/doc/refman/5.1/en/using-stack-trace.html

WB doesn't crash, it just repeatedly popup the dialog shown in the screen shot, and erroneously repaint its UI.

Is a stacktrace relevant in this case? If so, can you give me an easy way of doing that?

Please, check if the problem is repeatable with a newer version, 5.2.18, and inform about the results.

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".