MySQL Bugs: #58922: Exception raised in mysql workbench 'server administration'

Bug #58922	Exception raised in mysql workbench 'server administration'
Submitted:	14 Dec 2010 16:38	Modified:	4 Jan 2013 8:51
Reporter:	rick lavery	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S3 (Non-critical)
Version:	5.2.31 CE Revision 7115	OS:	Windows (Windows 7 64 bit with 4gb memory)
Assigned to:		CPU Architecture:	Any

Description:
I have existing connections defined under "SQL Development" that require me to set up an SSH tunnel and do some port forwarding.  Remotely I connect to each mysql instance on 3306 and forward to port X locally.  Then I use mysql workbench to connect to the local TCP connection that I set up on port X.  I don't have any problems connecting and maintaining the connection in SQL Development.  

When I start up "Server Administration" and import one of those connections or set up a new connection an exception is raised and I am asked to report a bug.

How to repeat:
This happens when I set up a new connection or import from an existing connection.

New Server Instance -> Highlight button "localhost" and click Next -> define connection name and set the port as appropriate and leave all other values as default (root, localhost) without any advanced options set and then click Next -> Get prompted for password / provide password / click OK ->  All button bars in the connection are checked automatically (it connects, gets mysql and OS version), everything looks good, click Next -> the next page shows up and I immediately get the message:

MySQL Workbench has encountered a problem

Attempted to read or write protected memory.  This is often an indication that other memory is corrupt.  

I have run the hardware vendor's memory check and it did not find any problems.

When the crash dialog appears, please, right click somewhere with no text in it and then select
the Copy stack trace option and attach what you get to this bug.

stack trace from error

Attachment: bug_58922_stack_trace.txt (text/plain), 1.59 KiB.

I couldn't repeat on Vista 64-bit.

I am verifying this bug because it happened twice (looks is something random).

as workaround you could setup the tunneling directly inside WB (set connection Method to "TCP over SSH").

I cannot reproduce the exception, but workbench doesn't allow you to specify correct administration properties for that kind of setup - that needs to be fixed

Bug #60137 was marked as a duplicate of this one.

Bug #60187 was marked as a duplicate of this one.

This is fixed as of MySQL Workbench 5.2.45, and here's the changelog entry:

  Importing a saved connection that used an SSH tunnel would throw
  an exception, and fail to import the connection.

Thank you for the bug report.