Bug #89191 Workbench CE 6.3.10 Intermittent Crashing
Submitted: 11 Jan 2018 14:58 Modified: 17 Jan 2018 17:32
Reporter: Ron Finnerty Email Updates:
Status: Can't repeat Impact on me:
None 
Category:MySQL Workbench Severity:S3 (Non-critical)
Version:6.3.10 OS:Microsoft Windows
Assigned to: CPU Architecture:Any

[11 Jan 2018 14:58] Ron Finnerty
Description:
Ever since I upgraded Windows 10 to the latest version (10.0.16299), when I click on a connection to open it, whether it is a conn to my local MySQL instance or a remote instance, I receive a message that "MySQL Workbench has encountered a problem. External component has thrown an exception." This happens intermittently. Once it does start happening, I cannot get a successful connection until I either restart Workbench or I restart my computer. This was not happening prior to the latest Windows Update that was installed. I have reinstalled Workbench with the latest downloaded msi on the mysql website, but that did not fix either.

How to repeat:
Keep opening up saved connections until the error occurs again.
[11 Jan 2018 19:25] Miguel Solorzano
Thank you for the bug report. Which server version are you trying to connect?. Thanks.
[11 Jan 2018 19:48] Ron Finnerty
Hello- the version is 5.6. I did some more testing today. I noticed that after I press the button to clear out the 'report bug' message, a connection tab opens, but does not show the connection name where it usually shows in the tab. Also, the query editor window is blank. But I can then press either a new SQL window, client connections, users & privileges, etc. and those will each open in their own windows- so there is functionality present, but only after opening a new tab for the particular function that I want to use. I can provide a screenshot if need be.
[12 Jan 2018 9:50] Chiranjeevi Battula
Hello Ron Finnerty,

Thank you for the feedback.
I could not repeat the issue at our end using with MySQL workbench 6.3.10 version.
Could you please provide repeatable test case (exact steps, screenshot,  log(preferably start with debug3) etc. - please make it as private if you prefer) to confirm this issue at our end?

Thanks,
Chiranjeevi.
[16 Jan 2018 13:21] Ron Finnerty
I have attached the debug3 log file as well as screenshots of what I am seeing. Before I performed these steps, I uninstalled WB again and deleted the Workbench folder in this path: C:\Users\<user>\AppData\Roaming\MySQL

The attached log/screenshots are after a fresh reinstallation.

Steps to repeat- there is only one step after launching WB, and that is to click on a saved connection to open it. Sometimes the connection will open cleanly, but most of the time the attached screenshots occur.
[17 Jan 2018 5:34] Chiranjeevi Battula
Hello Ron Finnerty,

Thank you for the feedback.
I could not repeat the issue at our end using with MySQL workbench 6.3.10 version.
As per your log file, It seems user don't have permissions to access the database.

Thanks,
Chiranjeevi.
[17 Jan 2018 17:32] Ron Finnerty
This issue has nothing to do with having access to a particular database. I have moved on to a different GUI client anyways.