MySQL Bugs: #55816: MySQL Workbench Keeps Crashing while using ERM diagraming tool

Bug #55816	MySQL Workbench Keeps Crashing while using ERM diagraming tool
Submitted:	7 Aug 2010 3:23	Modified:	18 Aug 2010 17:38
Reporter:	Scott McGlone	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S2 (Serious)
Version:	5.2.26 CE Rev 6432	OS:	Windows (XP Pro SP3)
Assigned to:	Assigned Account	CPU Architecture:	Any

Description:
When using the modeling tool, I repeatedly get an error that force closes Workbench.  It is generated after I double-click a table model to edit it.  I am able to restart Workbench, and continue making some changes.  After a couple edits, the error will get thrown again when trying to edit a table.

The error is:

# Microsoft Visual C++ Runtime Library
# Runtime Error!
#
# Program: C:\Pr...
#
# R6025
# - pure virtual function call

I did not encounter this error until after I syncronized the model with my database located at localhost.  I got some errors (which was correct) because I set up my FK constraint names incorrectly (I had duplicate names).  So I started going through the tables (currently 28 tables) and renaming the FK constraints.  I started getting the error when double-clicking tables to edit them.

How to repeat:
The issue seemed to happen after I tried to Synchronize the Model to the database on localhost.  I have since removed the database connection as well as the schema in an attempt to "unlink" the model from the database.  But the error persists.  The error is thrown when I double-click a table in the model to edit it.

I'm having the exact same problem.  Were you able to find a solution, Scott?

I have the same problem on Win7 Ultimate x64. Eventually, double-clicking a table results in a crash.

No, no solution yet - just a sort of "work around."  To "fix" it, I just made my changes to a table (via double-clicking it), saving it, then trying the next table.  If it crashed, I re-opened the app, selected the table I was trying to edit, made the changes, saved, then clicked on the next table.  If it crashed...I repeated that until all the changes I needed were complete.  I then re-connected to the local database, synchronized, and things seem to be okay.  I haven't made many changes since so I haven't crashed yet.  Not sure if it's still crashing.

One thing that did seem to sort of help: after I edited a table, I would close the table info section that pops up at the bottom *before* opening the next table.  Does this really help?  Probably not.  It seemed to though, so YMMV.

As far as I know, it's still a problem and something that needs to be addressed by the developers.

Thanks Scott!  It only became a problem for me after I added foreign keys to a table.  Now it crashes *every* time I switch between tables.  

Are you using a Dell by chance?

No, not using a Dell - I'm using a machine that I built.  I pretty sure the issue is not hardware related though.

Regarding the foreign keys - did you define your own names for the keys?  Did you create the keys using the relationship drawing tool or the Foreign Keys tab on the table properties?  I used the Foreign Keys tab, and incorrectly named the foreign keys (the first column).  If you use the Relationship drawing tool it will automatically name the FKs.  The tab however doesn't do that.  Make sure you use unique names.  I will have to do some more testing to see if the error is related to just that...

Okay, the issue is still occurring.  It seems to happen when I'm modifying FK's in the Foreign Key tab on the table properties, and then double-click another table to open.  I have done nothing with synchronizing and I'm working on a new schema now.

Same problem here on WindowsXP 32bit. I'm building a new Windows 7 64bit this week and will try over there as well, but it sounds like it's platform independent. Subscribing to thread...

I experience the same problems (win7 ultimate 64bit).

It always happens (in "Model tab") when I create a table, add columns and double click 'Add Table'. 

A work around for me is, after finishing the table, close the detail window of the table before creating a new table. This seems to work every time.

One nice side effect is that I save my model quite frequently :)

Hi Scott (and commenters maybe),

when the error-dialog shows up, please right-click the dialog and select "copy stack to clipboard" and add the copied information to the report.

thanks in advance

I can reproduce the crash. After adding a foreign key, double-clicking on a table, or choosing "Edit Table..." via the context menu will crash MySQLWorkbench (see error below). If I choose "Edit in new window", the soft WILL NOT crash.

The error is : 
Runtime Error! 
Progam:C:\Pr...
R6025
- pure virtual function call

@Johannes:

I tried what you asked, however the pop-up window does not give the option to copy the stack trace.  It's a modal window, with an "OK" button and the error message.  Right clicking on the window itself does nothing, right clicking on the title bar of the window gives only two options, "Move" and "Close."

Is there another way to get a dump of the stack trace?

I get the same error in 5.2.26 CE Rev 6432, couldn't yet happen to get it reproduced in 5.2.25 CE Rev 6303.

The error probably relates to this:
http://support.microsoft.com/kb/125749/EN-US/

this is a duplicate of Bug #55910