MySQL Bugs: #60187: Memory issue when creating a new server instance profile with port forwarding

Bug #60187	Memory issue when creating a new server instance profile with port forwarding
Submitted:	21 Feb 2011 7:35	Modified:	21 Feb 2011 9:33
Reporter:	Maarten van Leeuwen	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.31-CE revision 7115	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Installed MySQL Workbench on Windows 7. Tried to create a new server instance profile using portforwarding over ssh2. For the ssh connection and port forwarding I use putty. Connection is to localhost:3311.

How to repeat:
Reproduction:

Install MySQL Workbench on a Windows 7 machine. Configure Putty portforwarding to connect to a remote Linux (Redhat) database host. Now create a new server instance profile using standard TCP/IP with host localhost and the configured forwarded port, in my case I chose port 3311.

The wizard completes the first three steps, and fails at the fourth step:

- Specify host machine: localhost
- Database connection: port 3311, username set and password in vault.
- Test DB connection: Database connection tested successfully
- Management and OS: "MySQL Workbencj has encountered a problem. Attemtped to read or write protected memory. This is often an indication that other memory is corrupt"

Note: using the built-in "Standard TCP/IP over SSH" configuration works properly. The memory corruption only seems to happen when using an external ssh2 client for port forwarding.

This is, actually, a know problem. When you connect to localhost on Windows, Workbench assumes that it is local MySQL server and tries to find Windows service and my.ini for it. Probably this is just a duplicate of bug #58922.