Bug #51529 Fatal Error
Submitted: 25 Feb 2010 22:17 Modified: 25 Mar 2010 22:41
Reporter: Dennis Karcher Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version: OS:Windows (XP)
Assigned to: CPU Architecture:Any

[25 Feb 2010 22:17] Dennis Karcher
Description:
Exception = System.ObjectDisposedException
Message = Cannot access a disposed object.
Object name: 'WorkbenchOverviewForm'.
FullText = System.ObjectDisposedException: Cannot access a disposed object.
Object name: 'WorkbenchOverviewForm'.
   at System.Windows.Forms.Control.CreateHandle()
   at System.Windows.Forms.Form.CreateHandle()
   at System.Windows.Forms.Control.get_Handle()
   at System.Windows.Forms.Control.RectangleToScreen(Rectangle r)
   at MySQL.GUI.Workbench.WorkbenchOverviewForm.WheelMessageFilter.PreFilterMessage(Message& m)
   at System.Windows.Forms.Application.ThreadContext.ProcessFilters(MSG& msg, Boolean& modified)
   at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg)
   at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FPreTranslateMessage(MSG& msg)
   at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   at System.Windows.Forms.Application.Run(ApplicationContext context)
   at MySQL.GUI.Workbench.Program.Main(String[] Args)

How to repeat:
Used Scrolling Button on mouse while in data screen?
Seems to be repeatable...
[25 Feb 2010 22:41] MySQL Verification Team
Thank you for the bug report. Which version of WorkBench are you using? and could you please provide the output of Help->System Info.
[26 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".