MySQL Bugs: #59995: Attempted to read or write protected memory.

Bug #59995	Attempted to read or write protected memory.
Submitted:	7 Feb 2011 20:14	Modified:	7 Mar 2011 22:49
Reporter:	Michael Phillips	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.31 CE rev 7115	OS:	Windows (XP)
Assigned to:		CPU Architecture:	Any
Tags:	attempted to read, Memory, write protected

Description:

Exception = System.AccessViolationException
Message = Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
FullText = System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at Sql_editor.check_sql(Sql_editor* , Boolean )
   at MySQL.Grt.Db.Sql.Sql_editor.check_sql(Boolean sync)
   at MySQL.Grt.Db.Sql.SqlEditor.CheckSql(Boolean sync)
   at MySQL.GUI.Workbench.Plugins.DbMysqlRoutineEditor.RefreshFormData()
   at MySQL.GUI.Workbench.Plugins.ObjectEditorPlugin.CallRefreshFormData()
   at MySQL.GUI.Workbench.Plugins.ObjectEditorPlugin.RefreshFormDataInvoke()
   at MySQL.Grt.RunWrappedDelegate0<void\,void\,MySQL::Grt::DelegateSlot0<void\,void>::ManagedDelegate>.native_callback()
   at sigc.pointer_functor0<void>.()(pointer_functor0<void>* )
   at sigc.adaptor_functor<sigc::pointer_functor0<void> >.()(adaptor_functor<sigc::pointer_functor0<void> >* )
   at sigc.internal.slot_call0<sigc::pointer_functor0<void>,void>.call_it(slot_rep* rep)
   at wb.WBContext.flush_idle_tasks(WBContext* )
   at MySQL.Workbench.WbContext.flush_idle_tasks()
   at MySQL.GUI.Workbench.Program.timer_Tick(Object sender, EventArgs e)

How to repeat:
I open my routine and continue to update the code. This error has happened to me 4 times in the matter of a few times.

Thank you for the bug report. Could you please provide the step by step instructions how you got the application crash and the project model file if needed. Thanks in advance.

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".