MySQL Bugs: #70508: Crash on Copy and paste

Bug #70508	Crash on Copy and paste
Submitted:	3 Oct 2013 12:54	Modified:	16 Jul 2014 8:08
Reporter:	Pat Sinclair	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S2 (Serious)
Version:	6.0.7.11215	OS:	Windows (Windows 7 64bit)
Assigned to:		CPU Architecture:	Any
Tags:	Stack trace..

Description:
If I copy and paste a query from one query tab to another or in the same query tab, the system crashes.

How to repeat:
see above.

Suggested fix:
Not sure at this point.

Thank you for the bug report. I couldn't repeat please provide the backtrace and sample of query copied/pasted. Thanks.

When the message exception screen pop-up right click over the icon and select
copy stack trace to clipboard. Then paste it here. Thanks.

See below the stacktrace.
Exception = System.Runtime.InteropServices.SEHException
Message = External component has thrown an exception.
FullText = System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
   at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
   at System.Windows.Forms.Control.Invoke(Delegate method, Object[] args)
   at MySQL.Forms.DispatchControl.RunOnMainThread(function<void \* __cdecl(void)>* slot, Boolean wait)
   at MySQL.Forms.UtilitiesImpl.perform_from_main_thread(function<void \* __cdecl(void)>* slot, Boolean wait)
   at MySQL.MCallback2<void \*\,boost::function<void \* __cdecl(void)> const \&\,bool>.cpp_callback(function<void \* __cdecl(void)>* a1, Boolean a2)

I could not repeat this issue on latest GA version on Win7/Ubuntu 14.04 LTS.
Also, version 6.0.7 is old and many bugs were fixed since. Please
upgrade to current version 6.1.6, try with it and inform us if problem still
exists.

http://dev.mysql.com/downloads/workbench/

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".