Bug #67875 external component has thrown an exception

• Submitted: 11 Dec 2012 15:21
• Modified: 11 Jan 2013 16:17
• Reporter: Isaque Rodrigues
• Status: No Feedback
• Category: MySQL Workbench
• Severity: S3 (Non-critical)
• Version: 5.2.42
• OS: Windows (Microsoft Windows XP Professional Service Pack 3 (build 2600))
• CPU Architecture: Any
• Tags: WBBugReporter

[11 Dec 2012 15:21] Isaque Rodrigues

Description:
external component has thrown an exception

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

MySQL Workbench CE for Windows version 5.2.42  revision 9752
Configuration Directory: D:\Documents and Settings\stp283d\Application Data\MySQL\Workbench
Data Directory: C:\Programas\MySQL\MySQL Workbench CE 5.2.42
Cairo Version: 1.8.8
OS: Microsoft Windows XP Professional Service Pack 3 (build 2600)
CPU: 4x Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz, 3.2 GiB RAM
Active video adapter (0): Intel(R) HD Graphics Family
Installed video RAM: 256 MB
Current video mode: 1440 x 900 x 4294967296 cores
Used bit depth: 32
Driver version: 6.14.10.5361
Installed display drivers: igxprd32.dll
Current user language: Português (Portugal)

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:
external component has thrown an exception

[11 Dec 2012 16:17] MySQL Verification Team

Please try version 5.2.44. Thanks.

[12 Jan 2013 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".