Bug #67194 Cannot close MySQL Workbench
Submitted: 11 Oct 2012 14:34 Modified: 11 Nov 2012 14:41
Reporter: Jeff Moretti Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.42 OS:Windows (Microsoft Windows 7 Service Pack 1 (build 7601), 32-bit)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[11 Oct 2012 14:34] Jeff Moretti 
Description:
Cannot close program

----- Developer Notes -----

MySQL Workbench CE for Windows version 5.2.42  revision 9752
Configuration Directory: C:\Users\jmoretti\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
OS: Microsoft Windows 7  Service Pack 1 (build 7601), 32-bit
CPU: 4x Intel(R) Core(TM) i5-2520M CPU @ 2.50GHz, 3.2 GiB RAM
Active video adapter (0): Intel(R) HD Graphics 3000
Installed video RAM: 1428 MB
Current video mode: 1680 x 1050 x 4294967296 colors
Used bit depth: 32
Driver version: 8.15.10.2761
Installed display drivers: igdumd32.dll,igd10umd32.dll,igd10umd32.dll
Current user language: English (United States)

Exception = System.InvalidOperationException
Message = Handle is not initialized.
FullText = System.InvalidOperationException: Handle is not initialized.
   at System.Runtime.InteropServices.GCHandle.FromIntPtr(IntPtr value)
   at MySQL.Forms.ObjectImpl.FromUnmanaged(Object* object)
   at MySQL.Forms.TreeNodeViewImpl.root_node(TreeNodeRef* , TreeNodeView* self)
   at MySQL.MCallback1<mforms::TreeNodeRef\,mforms::TreeNodeView \*>.cpp_callback(TreeNodeRef* , TreeNodeView* arg1)
   at wb.WBContext.flush_idle_tasks(WBContext* )
   at MySQL.Workbench.WbContext.flush_idle_tasks()
   at MySQL.GUI.Workbench.Program.timer_Tick(Object sender, EventArgs e)

How to repeat:
open very complex database (lots of data/tables) then close mysql workbench
[11 Oct 2012 14:41] MySQL Verification Team 
Please try version 5.2.44. Thanks.
[12 Nov 2012 1: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".