MySQL Bugs: #67738: Executing short statements, i.e. deleting rows, droping a table, re-creating the

Bug #67738	Executing short statements, i.e. deleting rows, droping a table, re-creating the
Submitted:	28 Nov 2012 5:16	Modified:	28 Dec 2012 13:26
Reporter:	Marvin Haney	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: SQL Editor	Severity:	S3 (Non-critical)
Version:	5.2.44	OS:	Windows (Microsoft Windows XP Professional Service Pack 3 (build 2600))
Assigned to:		CPU Architecture:	Any
Tags:	WBBugReporter

Description:
Workbench crash

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

MySQL Workbench CE for Windows version 5.2.44  revision 9933
Configuration Directory: C:\Documents and Settings\mbhaney\Application Data\MySQL\Workbench
Data Directory: C:\Program Files\MySQL\MySQL Workbench CE 5.2.44
Cairo Version: 1.8.8
OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)
CPU: Mobile Intel(R) Pentium(R) 4 - M CPU 2.40GHz, 2.0 GiB RAM
Active video adapter (0): Mobility Radeon 7500 
Installed video RAM: 32 MB
Current video mode: 1024 x 768 x 4294967296 colors
Used bit depth: 32
Driver version: 5.1.2600.0
Installed display drivers: ati2dvag.dll
Current user language: English (United States)

Exception = System.Runtime.InteropServices.SEHException
Message = External component has thrown an exception.
FullText = System.Runtime.InteropServices.SEHException (0x80004005): External component has thrown an exception.
   at bec.GRTManager.flush_timers(GRTManager* )
   at MySQL.Workbench.WbContext.flush_timers()
   at MySQL.GUI.Workbench.MainForm.timer_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

How to repeat:
cannot... it seems to be an isolated incident.

Thank you for the bug report. So that exception isn't more repeatable (sequence of actions). Thanks.

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