Bug #50839 crash
Submitted: 2 Feb 2010 14:28 Modified: 2 Mar 2010 17:59
Reporter: Michael Garcia Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S3 (Non-critical)
Version:5.2.15 Beata OS:Windows (7 evaluation)
Assigned to: CPU Architecture:Any
Tags: window crash

[2 Feb 2010 14:28] Michael Garcia 
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:
I scrolled out.
But was not able to repeat it.
[2 Feb 2010 17:59] Johannes Taxacher 
do you remember where this was happening? where or what did you scroll out?
thx in advance.
[3 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".