MySQL Bugs: #76693: External component has thrown an exception

Bug #76693	External component has thrown an exception
Submitted:	14 Apr 2015 22:41	Modified:	17 Apr 2015 9:27
Reporter:	Chris Duke	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S1 (Critical)
Version:	6.2.4/6.2.5	OS:	Windows (W7 Pro 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	Edit trigger, lockup

Description:
I am simply editing an after insert trigger on a table.  I wrote the trigger in a text editor, I delete the existing trigger by using Ctrl+a then pressing delete.  I then get the message box telling me to report a bug.  The program is not responsive.  If I close the box and try to exit, the bug window returns.

I am running .NET 4.5 and the recommended ++ client.

How to repeat:
Open a model file with an existing trigger (After insert)
Use Ctrl +a to select all code in the trigger window
Press delete to clear
After a few seconds, the error pops up

Suggested fix:
Model is not usable - previously I was using .Net 4.0 - however, a new update in Windows causes an error in MSXML update unless .NET 4.5 is installed.

I had the same problem with 6.2.5 - so I uninstalled and went back to 6.2.4.  I suspect it might be a .NET issue.

Exception = System.ObjectDisposedException
Message = Cannot access a disposed object.
Object name: 'TransparentPopupControl'.
FullText = System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'TransparentPopupControl'.
   at System.Windows.Forms.Control.CreateHandle()
   at System.Windows.Forms.Form.CreateHandle()
   at System.Windows.Forms.Control.get_Handle()
   at TransparentPopupControl.Show(Int32 x, Int32 y)
   at MySQL.Forms.PopupWrapper.show(Popup* backend, Int32 spot_x, Int32 spot_y)
   at mforms.MenuItem.callback(MenuItem* )
   at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
   at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
   at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ToolStrip.WndProc(Message& m)
   at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Chris, can you please try the latest version of WB (6.3.2 RC)? I cannot reproduce this problem there and we had a number of changes wrt to triggers, so it might have been fixed already.

I have not had a chance to try the RC update - but here is what I am seeing.  

1.  I create a trigger.
2.  Open the trigger window to edit.
3.  Select all the code (Ctrl + a) then delete.
4.  Error window pops up

This leaves a trigger with blank code.  While I understand this should not be done, the error being thrown basically locks up the application.  My guess is that MSWB is trying to auto save or something?  

I cannot exit and restart - it must be closed using Task Manger.  Hopefully the next RC gives us some option or warning, as opposed to an error loop.

This is easy to reproduce on Win7 with WB 6.2.5 but with 6.3.2 I'm not able to reproduce this issue. Please could you try with 6.3.2 as Mike suggested and confirm from your end? I tried with BEFORE/AFTER for INSERT/UPDATE/DELETE etc triggers with no luck. If you are able to reproduce with 6.3.2 then please send us exact model file used etc.

Thanks,
Umesh

I first re-created the issue in 6.2.5.  Then uninstalled the program, installed 6.3.2 and tried to create the same problem with the same model file.  This time, I did not get a lock up.  Great!

Thank you for confirming that you didn't observe issue on 6.3.2.
WB 6.3.2 is release candidate and release candidates are believed to be stable, having passed all of MySQL's internal testing, and with all known fatal run time bugs fixed. I would suggest you to use 6.3.2.

Thanks,
Umesh