Bug #80325 | Workbench crashes when attempting to test a connection | ||
---|---|---|---|
Submitted: | 9 Feb 2016 23:32 | Modified: | 1 Jun 2016 1:29 |
Reporter: | John Krieger | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Workbench | Severity: | S3 (Non-critical) |
Version: | 6.3.6 Build 511 CE | OS: | Windows (7) |
Assigned to: | CPU Architecture: | Any |
[9 Feb 2016 23:32]
John Krieger
[10 Feb 2016 9:17]
MySQL Verification Team
Hello John, Thank you for the report and repeatable steps. Verified as described on Win7 with MySQL Workbench 6.3.6 CE (winx64). Thanks, Umesh
[10 Feb 2016 9:18]
MySQL Verification Team
-- debug info D:\>cd D:\Workbench\MySQL Workbench 6.3.6 CE (winx64) D:\Workbench\MySQL Workbench 6.3.6 CE (winx64)>MySQLWorkbench.exe -log-level=debug D:\Workbench\MySQL Workbench 6.3.6 CE (winx64)> Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indi cation that other memory is corrupt. at MformsButton.OnClick(EventArgs args) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.SendMessage(HandleRef hWnd, Int32 msg, IntPtr wParam, IntPtr lParam) at System.Windows.Forms.Control.SendMessage(Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.Control.WmCommand(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, Int Ptr lParam) at System.Windows.Forms.NativeWindow.DefWndProc(Message& m) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FP ushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at System.Windows.Forms.Form.ShowDialog(IWin32Window owner) at MySQL.Forms.FormWrapper.run_modal(Form* backend, Button* accept, Button* cancel) at mforms.MenuItem.callback(MenuItem* ) at System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e) at System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e) at System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ToolStrip.WndProc(Message& m) at System.Windows.Forms.ToolStripDropDown.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg) at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FP ushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData) at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context) at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context) at MySQL.GUI.Workbench.Program.Main(String[] Args) D:\Workbench\MySQL Workbench 6.3.6 CE (winx64)>
[1 Jun 2016 1:29]
Philip Olson
Posted by developer: Fixed as of the upcoming MySQL Workbench 6.3.7 release, and here's the changelog entry: Attempting to test custom connection details (a connection not yet created by Workbench) caused Workbench to fail and exit. The Test Connection functionality only functioned for existing or new connections. Thank you for the bug report.