Bug #100260 SQL Workbench doesn't launch at the very firts utilization
Submitted: 20 Jul 2020 6:01 Modified: 29 Jul 2020 12:37
Reporter: Joao Da Silva Email Updates:
Status: Can't repeat Impact on me:
Category:MySQL Workbench Severity:S1 (Critical)
Version: OS:Windows (Windows 10 Professional)
Assigned to: CPU Architecture:x86 (Intel® Core™ i7-8565U)
Tags: HUDFORM, MySQL Workbench

[20 Jul 2020 6:01] Joao Da Silva
I have just downloaded and installed the newest version of MySQL Workbench. The instalation and configuration process completed wit no problems. I have also checked out if the MySQL service was running and it was OK. Then, I started MySQL Workbench for the first time. . After clicking the local connection button, it starts clocking for many minutes, with no response. Finally, I clicked the Cancel button of the Open SQL Editor screen and the folowing message appeared: "Cannot Acces a Disposed Object. Object Name : 'HUDForm'.".

I have restarted the computer, but the results were the same.

I don't know if there is any relation with this bug, but before these full installation of MySQL was performed, I had a MySQL Workbench (only) installed, as a frontend for another DB and it was working fine. But this old installation was completely removed before the full, new instalation of MySQL.

How to repeat:
1. Launch MYSQL Workbench
2. Click on MySQL Connections -> Local
[29 Jul 2020 12:37] MySQL Verification Team
Hello Joao Da Silva,

Thank you for the bug report.
I tried to reproduce your issue on windows 10 with workbench 8.0.21 but I am not seeing any issues at my end. To investigate further this issue at our end, may I kindly request you to launch workbench under debug mode (-log-level=debug3) and provide unaltered workbench log file(more details about log are explained here - https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html). Thank you.

Ashwini Patil
[24 Sep 2020 12:07] MySQL Verification Team
Bug #100932 marked as duplicate of this one.