Bug #59606 MySql Workbench still crash when copy table SQL to clipboard
Submitted: 19 Jan 2011 9:33 Modified: 5 Apr 2011 16:38
Reporter: Angelo Mondati Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.31 OS:Windows (XP SP3)
Assigned to: CPU Architecture:Any
Tags: clipboard, copy, crash, SQL

[19 Jan 2011 9:33] Angelo Mondati
Description:
Workbench crashes after right-clicking on a table schema and choosing "Copy SQL to Clipboard".
However the problem does not always arise and sometimes performing that operation works.

How to repeat:
- Open a databse diagram
- Right click on a table schema
- Choose "Copy SQL to Clipboard"
[19 Jan 2011 10:15] Valeriy Kravchuk
When you'll get this crash again, please, right click somewhere in the error dialog box with no text and use Copy stack trace to clipboard context menu item. Send stack trace to this report.

I was not able to repeat this with any of my schemata.
[19 Jan 2011 10:56] Angelo Mondati
I have to add some details. The error seems to be catched. When it happens a "MySQL Workbench Unexpected Error" message appears (this message says that the clipboard operation failed) and I can only choose to close the message (and after this workbench seems to continue to operate) or report the bug.

However, if I close and restart workbench, immediatly another 'catched' error appears (which essentially claims that Invoke or BeginIvoke cannot be called on a control if a window handle has not been not created yet. Trying to copy the stack trace causes another error) and next an access violation arises (EventType : clr20r3     P1 : mysqlworkbench.exe     P2 : 5.2.31.7110     
P3 : 4cfee506     P4 : system.windows.forms     P5 : 2.0.0.0     P6 : 4889dee7
P7 : 1521     P8 : 17     P9 : system.invalidoperationexception).

I have to run workbench again and opening the last diagram it says that it was not properly closed and allows me to recover.

This is the stack trace when the original clipboard error arises ('Operazione richiesta sugli Appunti non riuscita' could be traslated as 'Requested clipboard operation failed'):

Exception = System.Runtime.InteropServices.ExternalException
Message = Operazione richiesta sugli Appunti non riuscita.
FullText = System.Runtime.InteropServices.ExternalException: Operazione richiesta sugli Appunti non riuscita.
   in System.Windows.Forms.Clipboard.ThrowIfFailed(Int32 hr)
   in System.Windows.Forms.Clipboard.SetDataObject(Object data, Boolean copy, Int32 retryTimes, Int32 retryDelay)
   in System.Windows.Forms.Clipboard.SetText(String text, TextDataFormat format)
   in System.Windows.Forms.Clipboard.SetText(String text)
   in MySQL.Forms.UtilitiesImpl.set_clipboard_text(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* content)
   in MySQL.MCallback1<void\,std::basic_string<char\,std::char_traits<char>\,std::allocator<char> > const \&>.cpp_callback(basic_string<char\,std::char_traits<char>\,std::allocator<char> >* arg1)
   in wb.WBContext.flush_idle_tasks(WBContext* )
   in MySQL.Workbench.WbContext.flush_idle_tasks()
   in MySQL.GUI.Workbench.Program.timer_Tick(Object sender, EventArgs e)
[5 Mar 2011 16:38] Valeriy Kravchuk
Please, check if this problem ever happens with a newer version, 5.2.32.
[5 Apr 2011 23:00] Bugs System
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".