Bug #67571 problema en mysql model
Submitted: 12 Nov 2012 21:45 Modified: 12 Dec 2012 22:25
Reporter: anibal avendaƱo Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:5.2.44 OS:Microsoft Windows (Microsoft (build 8250), 64-bit)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[12 Nov 2012 21:45] anibal avendaƱo
Description:
simplemente me aparecio la opcion de bug y que la reportada

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

MySQL Workbench CE for Windows version 5.2.44  revision 9933
Configuration Directory: C:\Users\user\AppData\Roaming\MySQL\Workbench
Data Directory: C:\Program Files (x86)\MySQL\MySQL Workbench 5.2 CE
Cairo Version: 1.8.8
OS: Microsoft  (build 8250), 64-bit
CPU: 4x Intel(R) Core(TM) i5 CPU       M 450  @ 2.40GHz, 7.8 GiB RAM
Current user language: Spanish (El Salvador)

Exception = System.NullReferenceException
Message = Object reference not set to an instance of an object.
FullText = System.NullReferenceException: Object reference not set to an instance of an object.
   at MySQL.Grt.UIForm.can_close()
   at MySQL.GUI.Workbench.ModelOverviewForm.CanCloseDocument()
   at MySQL.GUI.Workbench.MainForm.MainForm_FormClosing(Object sender, FormClosingEventArgs e)
   at System.Windows.Forms.Form.OnFormClosing(FormClosingEventArgs e)
   at System.Windows.Forms.Form.WmClose(Message& m)
   at System.Windows.Forms.Form.WndProc(Message& m)
   at MySQL.GUI.Workbench.MainForm.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

How to repeat:
cuando trato de salir de un modelo recien hecho me aparece bus
[12 Nov 2012 22:25] Miguel Solorzano
Please describe what you was doing?. Thanks.
[13 Dec 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".