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

Bug #55828	External component has thrown an exception
Submitted:	8 Aug 2010 23:52	Modified:	16 Aug 2010 4:07
Reporter:	Roel Van de Paar	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	5.2.26pre3	OS:	Any
Assigned to:		CPU Architecture:	Any

Description:
Exception = System.Runtime.InteropServices.SEHException
Message = External component has thrown an exception.
FullText = System.Runtime.InteropServices.SEHException: External component has thrown an exception.
   at wb.WBContextUI.finalize(WBContextUI* )
   at MySQL.Workbench.WbContext.finalize()
   at MySQL.GUI.Workbench.Program.Main(String[] Args)

How to repeat:
Make sure there are 0 bytes free on the drive where WorkBench is installed.

Not sure how helpful it is.

Attachment: backtrace_bug_55828.txt (text/plain), 14.85 KiB.

Reproduced. 

However, this time I got a different error (I was trying to open a model file):

-----
Cannot open document 'D:\TestDBs\sakila-db\Sakila...'
Error writing temporary file while opending document.: Broken pipe
-----

Unexpected error on trying to close workbench

Attachment: Unexpected Error.txt (text/plain), 5.81 KiB.

Dual error on closing workbench (ref file above)

Attachment: Dual_error_on_close.png (image/png, text), 63.44 KiB.

After clicking on "continue" on that second box in the image, a "copy stack trace to clipboard" is exactly the same as the one reported in the first entry on this bug.

Backtrace from "Cannot open document" (resolved with 5.2.25 symbols)

Attachment: backtrace_bug_55828_2.txt (text/plain), 24.23 KiB.

Further analysis of the coredumps from the crash above, based on some findings in other bugs:

-------
0:000> !gle -all
Last error for thread 0:
LastErrorValue: (Win32) 0 (0) - The operation completed successfully.
LastStatusValue: (NTSTATUS) 0xc0000008 - An invalid HANDLE was specified.
Wow64 TEB status:
LastErrorValue: (Win32) 0 (0) - The operation completed successfully.
LastStatusValue: (NTSTATUS) 0 - STATUS_WAIT_0
[...]
Last error for thread 8:
LastErrorValue: (Win32) 0 (0) - The operation completed successfully.
LastStatusValue: (NTSTATUS) 0xc0000008 - An invalid HANDLE was specified.
Wow64 TEB status:
LastErrorValue: (Win32) 0 (0) - The operation completed successfully.
LastStatusValue: (NTSTATUS) 0 - STATUS_WAIT_0
-------

I'll add more info on this soon.

I am quite convinced that the following bugs:

bug #55304 | bug #55776 | bug #55904 | bug #55774 | bug #55828

all have the same cause: some sort of issue with window/tab handles (note the "An invalid HANDLE was specified."). 

For more information, see the "[16 Aug 5:30] Roel Van de Paar" comment in bug #55996.

I am marking this bug as a duplicate of bug #55304 as that was the main one in which this issue was handled.