MySQL Bugs: #59423: Workbench crash after SSL remote restore/import command

Bug #59423	Workbench crash after SSL remote restore/import command
Submitted:	11 Jan 2011 17:16	Modified:	25 Feb 2011 18:03
Reporter:	Marc Schipperheyn	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench: Administration	Severity:	S2 (Serious)
Version:	5.2.31	OS:	Windows
Assigned to:		CPU Architecture:	Any

Description:
Connected over a SSL connection to remote server (Ubuntu/mysql 5.1).
Connection used public/private key,compression and a different than standard SSH port

went to import
import from file
selected file and clicked import
Workbench immediately crashed

How to repeat:
Connected over a SSL connection to remote server (Ubuntu/mysql 5.1).
Connection used public/private key,compression and a different than standard SSH port

went to import
import from file
selected file and clicked import
Workbench immediately crashed

Not sure if I can reproduce this anymore. Which makes me wonder why it happened in the first place. Two things I noticed:
1. I was logged in with insufficient privileges to perform the operation
2. the memory use on the server was very high

Unfortunately, I did reproduce it. I resized the remote server to eliminate the memory issue. Tried the import again, and after a long time of "Existing SSH Tunnel found, connecting..." it crashed again

I think the reason is that the system is trying to connect on a random port, not 3306, which of course is closed. It should be using 3306. WTF?

I confirm that the restore actually seems to have completed successfully which suggests that something bad happens at the end of it. There was no progress indication

If you'll ever see this crash again, please, right click somewhere in the error dialog box with no text and use Copy stack trace to clipboard context menu item. Send stack trace to this bug report.

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