MySQL Bugs: #100406: Cannot access a disposed object

Bug #100406	Cannot access a disposed object - 'HudForm'
Submitted:	1 Aug 2020 12:14	Modified:	2 Aug 2020 9:27
Reporter:	David Forster	Email Updates:
Status:	Verified	Impact on me:	None
Category:	MySQL Workbench	Severity:	S2 (Serious)
Version:	8.0.21, 8.0.22, 8.0.23, 8.0.28, 8.0.32, 8.0.36, 8.0.38	OS:	Windows
Assigned to:		CPU Architecture:	x86

Description:
When attempting to connect to a database requiring SSL, but SSL set to 'No' in WorkBench, I pressed cancel on the "Opening SQL Editor" and it presented me with the error:

"Cannot access a disposed object
Object name: 'HUDForm'."

How to repeat:
Target DB user set to require SSL.
In WorkBench, set SSL to 'No'.
Attempt to connect to the Database.
Then press 'Cancel'.

Error appears.

Hello David Forster,

Thank you for the report and feedback.
Observed this with WB 8.0.21 on Win10.

regards,
Umesh

Bug #100405 marked as duplicate of this one

Bug #100412 marked as duplicate of this one

https://bugs.mysql.com/bug.php?id=100466 marked as duplicate of this one.

MySQL Team any update on this fix even iam facing the same issue

https://bugs.mysql.com/bug.php?id=100539 marked as duplicate of this one.

Hi, is there a solution to this problem? I have encountered the same problem.

same to me

Working through the SQL for Beginners: Learn SQL using MySQL and Database Design course.

Unable to load the root to access the Users and Privileges. Error: Cannot access a disposed object. Object name: 'HUDForm'.

Hi all, 

I managed to open MYSQL workbench after downloading the older version 
8.0.20 instead of 8.0.21. 

Comment from my school IT staff:

You can try installing an older workbench. It's a bug in SQL workbench for Windows 10.

Bug #100684 marked as duplicate of this one

i have experienced the same problem.

Bug #100693 marked as duplicate of this one

https://bugs.mysql.com/bug.php?id=100706 marked as duplicate of this one.

After installation of 8.0.21: tying to connect to localhost takes a VERY long time, pressing Cancel returns this error. Is there a solution to this??

https://bugs.mysql.com/bug.php?id=100753 marked as duplicate of this one.

https://bugs.mysql.com/bug.php?id=100753 marked as duplicate of this one.

Bug #100848 marked as duplicate of this one

Observed with MySQL Workbench 8.0.21, on Windows 10 .

In my case, error appears when the connection is configured as: 

    USE SSL: "If available"

Setting this configuration as:

    USE SSL: "No"

Error does not appears.

https://bugs.mysql.com/bug.php?id=100884 marked as duplicate of this one.

https://bugs.mysql.com/bug.php?id=100942 marked as duplicate of this one.

https://bugs.mysql.com/bug.php?id=101030 marked as duplicate of this one.

Bug #101067 marked as duplicate of this one

Yes, a problem. New to Oracle/Mysql.  How in the world do you contact anyone? I know my software has been free but!!  Does anyone post a running update on what is happening in terms of a solution?  Do I delete Mysql, find an older version? Error page shows outstanding for 66 days.

https://bugs.mysql.com/bug.php?id=101094 marked as duplicate of this one.

Bug #101116 marked as duplicate of this one

https://bugs.mysql.com/bug.php?id=101121 marked as duplicate of this one.

Bug #101214 marked as duplicate of this one

Bug #101223 marked as duplicate of this one

Same here. Why is this happening?

Bug #101261 marked as duplicate of this one

Bug #101449 marked as duplicate of this one

https://bugs.mysql.com/bug.php?id=101458 marked as duplicate of this one.

Experienced the same error. The workaround is to install an slightly older version. I used v8.0.19 instead of v8.0.22. Maybe even .21 works for you... didn't try.
You can find older versions at https://downloads.mysql.com/archives/workbench/

https://bugs.mysql.com/bug.php?id=101543 marked as duplicate of this one.

Bug #101655 marked as duplicate of this one

https://bugs.mysql.com/bug.php?id=101666 marked as duplicate of this one.

https://bugs.mysql.com/bug.php?id=101738 marked as duplicate of this one.

Bug #101753 marked as duplicate of this one

Bug #101774 marked as duplicate of this one

Bug #101844 marked as duplicate of this one

I created another connection and called it "Local instance 3305" and it worked to open the Workbench.

I created another connection and called it "Local instance 3305" and it worked to open the Workbench.

Had the same problem. Did the same as above (created new connection called Local instance 3055) on MySQL Workbench 8.0.22 and it worked.

https://bugs.mysql.com/bug.php?id=102074 marked as duplicate of this one.

Bug #102148 marked as duplicate of this one.

Bug #102146 marked as duplicate of this one.

Started getting this regularly. Reinstalled Community v8.0.22 and it went away initially but once I duplicated a working connection it started again - I had only executed a single script (to create a default 4 table db!)
Now will have to do it all again :(
Is there NO fix/workaround/update?

HUD Form Bug

Attachment: HUDFormBug.png (image/png, text), 94.05 KiB.

Hmmm! Following my previous comment, turns out there is a NEW update - you need to do a catalogue update and suddently v8.0.23 arrives...

To do this run the mysql_community installer.msi again and tap the Catalog(ue) button...

So tried this and nope, bug still there :(
Will reinstall completely (remove all mySQL traces before doing so) and try again

https://bugs.mysql.com/bug.php?id=102361 marked as duplicate of this one.

https://bugs.mysql.com/bug.php?id=102453 marked as duplicate of this one.

https://bugs.mysql.com/bug.php?id=102499 marked as duplicate of this one.

Bug #102547 marked as duplicate of this one

Bug #102546 marked as duplicate of this one

https://bugs.mysql.com/bug.php?id=102726 marked as duplicate of this one.

Bug #100406--- seeing the same issue

Bug #102780 marked as duplicate of this one

https://bugs.mysql.com/bug.php?id=102803 marked as duplicate of this one.

https://bugs.mysql.com/bug.php?id=102837 marked as duplicate of this one.

Bug #102879 marked as duplicate of this one

When opening workbench and connecting to a local instance.Its showing 

"Cannot access a disposed object
Object name: 'HUDForm'."

and another popup showing MySQL workbench has stopped working

same thing happens to me - is there a resolution for this?

Bug #103094 marked as duplicate of this one.

The bug screen shot

Attachment: Screenshot 2021-03-26 122425.png (image/png, text), 90.81 KiB.

Same bug i'm facing, don't know how to resolve it.

Bug #103151 marked as duplicate of this one.

Here is something I found. 

I was testing my connection and stored a user/pass other than root/(Main password).

I clicked on "edit connection" for the basic installation and changed the information in there back to root/(Main password). I specifically used the "clear" button. 

Before doing this the program bugged out every time and would tell me to hang on while the connection was made then give me the HUDform error> Close Workbench.

I can now access the program with no problems. Ill update if it occurs again.

I have had this sporadically with 8.0.22 and 8.0.23 but I found ONE way to "fix" it. 
It happens periodically (perhaps the db is in a weird state) BUT the issue is the connection - NOT the data or dbServer. 
I found that clearing & resetting the password for the affected user on that database (and schema?) within the connection did help and the HUDForm went away. 
Maybe the connection is left in an indetermine state when a failure of some db operation or commit fails and this causes the connection be blocked in one "view" but active in another? No idea. 
HTH
Mark

https://bugs.mysql.com/bug.php?id=103313 marked as duplicate of this one.

Stopping the MySQL80 service (in Windows services) , opening the connection and then restarting the service fixed the problem for me. Curious if it is fixed permanently, though. Will find out next time I open the workbench, I guess.

Stopping the MySQL80 service (in Windows services) , opening the connection and then restarting the service fixed the problem for me. Curious if it is fixed permanently, though. Will find out next time I open the workbench, I guess.

Bug #103352 marked as duplicate of this one

Bug #103509 marked as duplicate of this one

Hi there

I am currently facing this issue after I tried to reset my root password and restarted the computer

Anyway to solve this issue

This happened to me after I changed my password on the server to a mysql_native_password.   (I don't know if it's simply that I changed it, or that I changed to mysql_native_password).  But I was able to fix it by clearing the password associated with the stored connection (and then storing it again)

This happened to me after I changed my password on the server to a mysql_native_password.   (I don't know if it's simply that I changed it, or that I changed to mysql_native_password).  But I was able to fix it by clearing the password associated with the stored connection (and then storing it again)

@Peter_Fales, I also had the same issue and did as you suggested and it worked. Thank You.

In my case this happens 100% of the time when I do the following.
----------------------------------------------------------------------
Version: 8.0.22
Process Name:	MySQLWorkbench.exe : C:\Program Files\MySQL\MySQL Workbench 8.0 CE\MySQLWorkbench.exe
Process Architecture:	x64
Exception Code:	0xE0434352
An unhandled exception of type 'System.ObjectDisposedException' occurred in System.Windows.Forms.dll
Cannot access a disposed object.
OS Version:	10.0.18363
CLR Version(s):	4.8.4300.0
Python Version: 3.8.5
-----------------------------------------------------------------------
I have around 30 connections saved in Workbench and my company makes us change the MySQL password frequently. Whenever I have to change my password, the next time I go into Workbench it will crash if I double click on one of my saved connections. It doesn't really crash until I click cancel due to it hanging indefinitely. A peek into the logs shows it is getting access denied from the server (probably because I saved my password in the connection).

wb.log : 14:14:51 [ERR][  GRTDispatcher]: exception in grt execute_task, continuing: Exception: Access denied for user 'xxxxx'@'10.x.x.x' (using password: YES)
14:14:51 [ERR][  GRTDispatcher]: worker: task 'execute sql queries' has failed with error:.Access denied for user 'xxxxx'@'10.x.x.x' (using password: YES)
This is repeated until I click cancel button.

To resolve this, instead of clicking on the connection, I right click 'Edit Connection', click Test Connection, then it prompts me for a password. 
Once I use the new password, and click Save Password, the connection succeeds and from then on everytime I open that saved connection, it doesn't hang, until the next password change. 
All these servers with the same credentials is a pain to maintain, but if I remember to Test Connection before trying to connect, I never see this crash as a result of the hang.

Bug #104671 marked as duplicate of this

Bug #104775 marked as duplicate of this one.

Bug #104916 marked as duplicate of this one

Bug #105227 marked as duplicate of this one

I deleted all conections and I created again the conextions. Fixed.

I tried Douglas Richards's way and it worked

Bug #107631 marked as duplicate of this one

Bug #110038 marked as duplicate of this one

Bug #110344 marked as duplicate of this one

Bug #116347 marked as duplicate of this one