Bug #51445 Issue when replication the model on my database
Submitted: 24 Feb 2010 4:50 Modified: 25 Mar 2010 2:29
Reporter: Laurent Charmes Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench: Modeling Severity:S2 (Serious)
Version:5.2.15 OS:Microsoft Windows (Windows 7 32 bits)
Assigned to: CPU Architecture:Any

[24 Feb 2010 4:50] Laurent Charmes
Description:
Exception = System.AccessViolationException
Message = Tentative de lecture ou d'écriture de mémoire protégée. Cela indique souvent qu'une autre mémoire est endommagée.
FullText = System.AccessViolationException: Tentative de lecture ou d'écriture de mémoire protégée. Cela indique souvent qu'une autre mémoire est endommagée.
   à sigc.internal.signal_emit0<void,sigc::nil>.emit(signal_impl* impl)
   à sigc.signal0<void,sigc::nil>.emit(signal0<void\,sigc::nil>* )
   à mforms.Wizard.next_clicked(Wizard* )
   à MySQL.Forms.WizardImpl.nextClick(Object sender, EventArgs arguments)
   à System.Windows.Forms.Control.OnClick(EventArgs e)
   à System.Windows.Forms.Button.OnClick(EventArgs e)
   à System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   à System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   à System.Windows.Forms.Control.WndProc(Message& m)
   à System.Windows.Forms.ButtonBase.WndProc(Message& m)
   à System.Windows.Forms.Button.WndProc(Message& m)
   à System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   à System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   à System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

How to repeat:
well i can repeat it on my computer :

i ve updated one table with 2 new fields TINYINT
then Database/Synchronize Model
[25 Feb 2010 2:29] Miguel Solorzano
Thank you for the bug report. Could you please try version 5.2.16. Thanks in advance.
[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".