Bug #50898 Exception = System.ObjectDisposedException
Submitted: 4 Feb 2010 1:56 Modified: 4 Mar 2010 12:13
Reporter: yuan zhengwen Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.15 OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[4 Feb 2010 1:56] yuan zhengwen
Description:
Exception = System.ObjectDisposedException
Message = 无法访问已释放的对象。
对象名:“WorkbenchOverviewForm”。
FullText = System.ObjectDisposedException: 无法访问已释放的对象。
对象名:“WorkbenchOverviewForm”。
   在 System.Windows.Forms.Control.CreateHandle()
   在 System.Windows.Forms.Form.CreateHandle()
   在 System.Windows.Forms.Control.get_Handle()
   在 System.Windows.Forms.Control.RectangleToScreen(Rectangle r)
   在 MySQL.GUI.Workbench.WorkbenchOverviewForm.WheelMessageFilter.PreFilterMessage(Message& m)
   在 System.Windows.Forms.Application.ThreadContext.ProcessFilters(MSG& msg, Boolean& modified)
   在 System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg)
   在 System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FPreTranslateMessage(MSG& msg)
   在 System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   在 System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   在 System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   在 System.Windows.Forms.Application.Run(ApplicationContext context)
   在 MySQL.GUI.Workbench.Program.Main(String[] Args)

How to repeat:
mysql-workbench-oss-5.2.15a-beta-win32-noinstall.zip

Suggested fix:
mysql-workbench-oss-5.2.15a-beta-win32-noinstall.zip
[4 Feb 2010 12:13] Susanne Ebrecht
What did you do for getting this exception?
[5 Mar 2010 0: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".