MySQL Bugs: #45773: Workbench Lost Objects + Crash

Bug #45773	Workbench Lost Objects + Crash
Submitted:	26 Jun 2009 5:45	Modified:	28 Aug 2009 9:04
Reporter:	jed davidow	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench	Severity:	S1 (Critical)
Version:	5.1.14/5.1.15	OS:	Windows (Vista SP2)
Assigned to:	Alexander Musienko	CPU Architecture:	Any
Tags:	crash, lost objects

Description:
This afternoon I was working with 5.1.14 OSS, using it on my desktop to connect to the DB server (5.1.34) on my laptop. I also had a Query Browser open on my laptop.

It was easier to 'code' SQL in the Query browser, so I eventually stopped using the WB tool. But, after I had created a few procedures and added some test data, I used the Sync command to push the changes back into WB, saved the WB file and checked it into my source control.

After that, I wrote some code to access the laptop DB via ODBC on the Desktop, and successfully called my new stored procedures.

Everything looked good, so I shut down the desktop and allowed my laptop to sleep.

6 hours later. I get some errors, so I inspect the DB on the laptop, and several of the new procedures I wrote are missing. HOWEVER, the last thing I did was to modify an older procedure to access the new ones. This one is fine! But the newer procedures are lost.

I open the WB file and the model looks OK. However, WB crashes when I try to sync, pushing changes to the Source. I then backed up and tried to Forward Engineer, and this crashes too. Both with and without checking the DROP Objects option.

Unfortunately, I did not have logging turned on when this happened, so I have no idea why the procedures were dropped. There is test data that I added to the DB right before I shut down, so I cannot understand why some changes to tables and some procedures have been lost.

I am not sure what information you need.

How to repeat:
Load example.sql;
Load Workbench file;
Attempt to forward engineer/sync.

Note, these are the files AFTER the objects disappeared.

Crash data from dialog

Attachment: crash.txt (text/plain), 5.12 KiB.

Database file with missing objects

Attachment: cpv.sql (application/octet-stream, text), 21.44 KiB.

Workbench file

Attachment: cpvB.mwb (application/octet-stream, text), 20.57 KiB.

Thank you for the bug report. You said? Load example.sql I didn't find that file attached, could you please provided it?. Thanks in advance.

My apologies, the DB is in the cpv.sql file.

Thank you for the feedback.

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at sigc.internal.signal_emit0<void,sigc::nil>.emit(signal_impl* impl)
   at sigc.signal0<void,sigc::nil>.emit(signal0<void\,sigc::nil>* )
   at mforms.Wizard.next_clicked(Wizard* )
   at MySQL.Forms.WizardImpl.nextClick(Object sender, EventArgs arguments)
   at System.Windows.Forms.Control.OnClick(EventArgs e)

<cut>

Crash fixed

this has been fixed.
fix will be included in 5.1.17

An entry was added to the 5.1.17 changelog:

MySQL Workbench crashed and also lost procedure objects when attempting to synchronize with a live database.