MySQL Bugs: #59857: Typing in "Apply SQL Script..." dialog throws AccessViolationException

Bug #59857	Typing in "Apply SQL Script..." dialog throws AccessViolationException
Submitted:	31 Jan 2011 23:42	Modified:	1 Mar 2011 7:41
Reporter:	Yvan Rodrigues	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.31	OS:	Any
Assigned to:		CPU Architecture:	Any
Tags:	AccessViolationException, ALTER TABLE, apply, exception, textbox

Description:
Entering text in a TextBox throws AccessViolationException.

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 mforms.TextBox.key_event(TextBox* , KeyCode , ModifierKey , basic_string<char\,std::char_traits<char>\,std::allocator<char> >* )
   at MySQL.Forms.TextBoxEx.ProcessCmdKey(Message& msg, Keys keyData)
   at System.Windows.Forms.Control.PreProcessMessage(Message& msg)
   at System.Windows.Forms.Control.PreProcessControlMessageInternal(Control target, Message& msg)
   at System.Windows.Forms.Application.ThreadContext.PreTranslateMessage(MSG& msg)

How to repeat:
- Right click any table | Alter Table...
- Make any change to the table
- Click Apply
- Dialog entitled "Review the SQL Script to be Applied on the Database" appears
- Start typing in the TextBox under the "SQL Statement(s):" Label
- BOOM!

Suggested fix:
(a) make TextBox read-only OR
(b) ensure memory is allocated to accomodate user input

WORKAROUND:
Stop typing in that box, dummy.

Not repeatable on Mac OS X.

I can not repeat this on 32-bit Windows XP SP3 also. Please, send the output of Help > System Info menu item.

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