Bug #105025 Mysql Workbench goes unresponsive in MacOSX 11 when editing a script
Submitted: 23 Sep 2021 21:32 Modified: 24 Sep 2021 13:25
Reporter: Raul Banderas Email Updates:
Status: Duplicate Impact on me:
None 
Category:MySQL Workbench: SQL Editor Severity:S1 (Critical)
Version:8.0.26 OS:MacOS (11.3 (20E232))
Assigned to: CPU Architecture:x86 (MacOS Big Sur)
Tags: MacOS BigSur

[23 Sep 2021 21:32] Raul Banderas
Description:
Almost all the times I'm editing a script, especially when moving something in the WHERE clause, MySQL Workbench stops responding forever and I have to do a Force Quit for it. This happens very very often, that I decided to use an external editor to edit the queries and copy/paste them into the Workbench editor only to run them there. This is very annoying, and I hoped this could be solved in the new version 8.0.26 but is not. :(

My partner uses Workbench on Windows and he doesn't have this problem.

I have experienced this bug since I use MySQL Workbench (about 2+ years now)

How to repeat:
Open MySQL Workbench on Mac OS version 10+ or 11+ (I have MacOS 11.3 Big Sur) open some query with a considerably long WHERE clause on in. For example a view query. Next, try to move some of the conditions on the WHERE clause and, at some point, MySQL Workbench will stop responding and it will never come back :(

Suggested fix:
No clue
[23 Sep 2021 21:48] Raul Banderas
image with the moment where MySQL Workbench on Mac goes unresponsive

Attachment: MySQLWorkbench-bug-unresponsive-Mac.png (image/png, text), 315.30 KiB.

[23 Sep 2021 21:52] Raul Banderas
screenshot showing MySQL Workbench is not responding

Attachment: MySQLWorkbench-needs-forcequit.png (image/png, text), 256.43 KiB.

[24 Sep 2021 13:25] MySQL Verification Team
Hello Raul Banderas,

Thank you for the bug report.
This is most likely duplicate of Bug #98775, please see Bug #98775.
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.

Regards,
Ashwini Patil