Bug #51158 Closed application
Submitted: 13 Feb 2010 2:57 Modified: 18 Mar 2010 9:40
Reporter: hahmael taher Email Updates:
Status: No Feedback Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.15 OSS, Revision 5053 OS:Windows
Assigned to: CPU Architecture:Any

[13 Feb 2010 2:57] hahmael taher
Exception = System.ObjectDisposedException
Message = No se puede obtener acceso al objeto eliminado.
Nombre del objeto: 'WorkbenchOverviewForm'.
FullText = System.ObjectDisposedException: No se puede obtener acceso al objeto eliminado.
Nombre del objeto: 'WorkbenchOverviewForm'.
   en System.Windows.Forms.Control.CreateHandle()
   en System.Windows.Forms.Form.CreateHandle()
   en System.Windows.Forms.Control.get_Handle()
   en System.Windows.Forms.Control.RectangleToScreen(Rectangle r)
   en MySQL.GUI.Workbench.WorkbenchOverviewForm.WheelMessageFilter.PreFilterMessage(Message& m)
   en System.Windows.Forms.Application.ThreadContext.ProcessFilters(MSG& msg, Boolean& modified)
   en System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg)
   en System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FPreTranslateMessage(MSG& msg)
   en System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
   en System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
   en System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
   en System.Windows.Forms.Application.Run(ApplicationContext context)
   en MySQL.GUI.Workbench.Program.Main(String[] Args)

How to repeat:
creating foreign keys between two tables, foreign key with similar name.
[18 Feb 2010 9:40] Valeriy Kravchuk
Thank you for the problem report. Please, check if the same problem happens with a newer version, 5.2.16.
[19 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".