MySQL Bugs: #56605: Reported a crash but did not close Workbench upon requestion new connection.

Bug #56605	Reported a crash but did not close Workbench upon requestion new connection.
Submitted:	7 Sep 2010 0:22	Modified:	7 Oct 2010 13:29
Reporter:	Matt Langley	Email Updates:
Status:	No Feedback	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	5.2.26CE rev 6432	OS:	Windows (XPSP3)
Assigned to:		CPU Architecture:	Any
Tags:	Workbench crash connection

Description:
Double clicked on server on home page to create a new SQL connection and it reported a crash and requested that I report it.

I already had one connection, but requested another.

Workbench did not close, even after clicking the close button on the error dialog, and seems to work fine.

How to repeat:
Basic steps are:

Open Workbench (with server connections defined).
Double click on a server to create a SQL connection.
Click on Home Page tab.
Double click on a server to create a SQL connection.

I should imagine there's more to it than that, so it probably won't be immediately reproducible, but that's what I did.

I actually did use the first connection for a week or so before requesting a new one, and do have entire other copy of Workbench running as well. I'm also probably running low on memory (loads of Firefox windows open), although no virtual memory warnings.

Hi Matt,
as i understand, this is not exactly repeatable on your system as well (I don't see this behavior on my systems)? If you encounter the problem again, please right-click somewhere in that "report a problem" dialog and select "copy stack to clipboard". then add the copied information to this report.
thanks in advance

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