MySQL Bugs: #48891: Workbench Crashes when opening .mwb file

Bug #48891	Workbench Crashes when opening .mwb file
Submitted:	19 Nov 2009 7:53	Modified:	25 Nov 2009 11:34
Reporter:	Ryan Wilson	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.2.8 r4572	OS:	MacOS (10.6.2)
Assigned to:	Mike Lischke	CPU Architecture:	Any

Description:
I have been working on modeling a new schema, saving often because of frequent Workbench crashes (on things such as double-clicking an existing column, selecting the foreign keys tab, etc).  After the most recent crash, Workbench crashes every time I try to reopen the saved .mwb file.  Previously, I could always open the .mwb file after a crash, but not as of the last crash.

This is symptomatically identical to a "Closed" bug from a couple years ago, #32968.

How to repeat:
Try to open a file that seems to cause the crash.

Suggested fix:
If the crash is caused by attempting to load a corrupted, or otherwise bad, .mwb file, perhaps a routine to check the validity of a .mwb file before trying to load it.

I have this, too. Bad.

Fixed in 5.2.

This is only the fix to avoid WB crashing with invalid model files like this one. It still remains to investigate why the file got corrupted. But this is a separate issue.

I should add, a corrupted file can usually not be recoverd, unless it is just a small glitch which is wrong. In this case however the entire main content is gone. Sorry for that.

WB doesn't crash on opening that model, it identifies a problem inside the file and reports this accordingly. we are trying to track down the source of corruption in the first place though.
fix will be included in 5.2.9

Two notes I forgot to mention before:
- The app may have crashed while saving.  It happened right as I pressed ctrl+s, and that could explain how the .mwb file became corrupted.
- After creating the bug report, I found a .mwb.bak file in the same directory, which, after renaming, I was able to open without problem.

If I remember correctly, the backup file contained all of my work, except what I had changed since the last save.  My apologies for not updating the bug report at that time.

An entry has been added to the 5.2.9 changelog:

MySQL Workbench crashed on opening a model file. This appeared to be due to MySQL Workbench causing corruption in the model file.

I have just downloaded MySQL Workbench 6.3.3 on my MacPoo Pro while opening an .mwb file provided to me for analysis, a window open while information about the model and after half a second WB crashes.

In addition to my last comment, I would like to mention that opening the sakila_fill.wmb file provided in the kit crashes as well the same way.

Cedric, please open a new bug report if you think a bug must be tracked and fixed. Don't hijack old and already close bug reports for that.