Bug #110776 Crash when accessing a non available DB
Submitted: 24 Apr 7:55 Modified: 4 Sep 11:52
Reporter: Estanislao Gonzalez Email Updates:
Status: Need Feedback Impact on me:
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:8.0.33 OS:MacOS
Assigned to: MySQL Verification Team CPU Architecture:ARM
Tags: Crash (non fatal)

[24 Apr 7:55] Estanislao Gonzalez
When trying to access a port without a DB behind, the Application crashes.

Seen at least since 8.0.31.

The common use-case is having a tunnel. If the tunnel is gone, attempting to access the DB either by issuing an SQL or simply trying to create a new connection makes the application crash. No message is displayed.

How to repeat:
1) Connect to a DB though a tunnel
2) Remove the tunnel
3) try to access the Db via MySQL Workbench

(might be reproducible in many other ways)
[26 Apr 12:43] MySQL Verification Team
Hello Estanislao Gonzalez,

Thank you for the bug report.
Are you able to connect to db/create a connection when tunnel is available?
Also, are you able to connect to db in remote server?

Ashwini Patil
[26 Apr 15:06] Estanislao Gonzalez
Yes, everything works perfectly.
E.g. If I close the application and drop the tunnel, I can then open the application again and as soon as I try to start a connection to that particular db, the app crashes without giving any information.
I think the connection needs to exist, be valid and saved at least once. After that, if the db doesn't exist (I think the same happened with local containers but I'm not sure... I can check if it's important)

What I expected is the message that the connection to the DB failed. Instead it simply crashes.
[4 Sep 11:52] MySQL Verification Team

Thank you for the details.
Please upgrade MySQL workbench to latest version i.e 8.0.34 and let us know if you are still facing the issue. Thanks.

Ashwini Patil