Bug #91444 Workbench non-responsive when other transaction-heavy client running
Submitted: 27 Jun 2018 15:05 Modified: 27 Mar 2020 12:30
Reporter: Danny Holstein Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench Severity:S5 (Performance)
Version:6.3.9 OS:Windows (Microsoft Windows 10 Enterprise)
Assigned to: CPU Architecture:Any
Tags: WBBugReporter

[27 Jun 2018 15:05] Danny Holstein 
Description:
----[For better reports, please attach the log file after submitting. You can find it in C:\Users\dholstei\AppData\Roaming\MySQL\Workbench\log\wb.log]

While running Excel VBA code to import thousands of files into MySQL, MySQL Workbench becomes completely unresponsive. When I switch the Excel ODBC client to that of MariaDB, Workbench is unaffected and behaves normally.

I'm running:

   Workbench X64
   Connector X86

What's going on? I've always known MySQL client libraries/DLLs are multi-threaded. How is it it's not multi-threaded at the OS level?

How to repeat:
Use Excel to create thousands of transactions to a DB while running Workbench.

Suggested fix:
Seeing as switching to a MariaDB client fixes the hang, I'm wondering if there's a re-entrancy issue in the client library
[27 Jun 2018 15:15] MySQL Verification Team 
Thank you for the bug report. MariaDB is unsupported server. Thanks.
[27 Jun 2018 15:36] Danny Holstein 
This should not have been marked as "unsupported". How is the MySQL Client being messed up and not allowing other applications to access it unsupported?

It's as if a computer scanned the bug report and equated one key word with "unsupported".
[27 Jun 2018 15:37] Danny Holstein 
I am using a MySQL server and the MySQL Connector and ODBC
[27 Jun 2018 16:02] MySQL Verification Team 
Thank you for the feedback. Sorry but I didn't see any mention on your description which MySQL server version are you using. Thanks.
[27 Jun 2018 16:10] Danny Holstein 
Since the problems exist on the client side only, I didn't think the server details were relevant, but it's 5.7.19-Community
[28 Jun 2018 10:34] Chiranjeevi Battula 
Hello Danny Holstein,

Thank you for the bug report.
This is most likely duplicate of Bug #75109, please see Bug #75109

Thanks,
Chiranjeevi.
[28 Jun 2018 11:28] Danny Holstein 
You'll have to convince me it's a duplicate, I disagree.

This is, most definitely, a client driver issue, it is affected by other applications (Excel) using ODBC. When I use different drivers, the issue goes away.
[27 Mar 2020 12:30] MySQL Verification Team 
Hello Danny Holstein,

Thank you for your valuable feedback.
We have revisited this issue and discussed with WB Developer who analyzed and concluded that the symptoms are the same i.e in Bug #75109. 
Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. 
Thank you for your interest in MySQL.

Regards,
Ashwini Patil