Description:
I downloaded mysql-workbench-community-8.0.32-macos-x86_64.dmg
from dev.mysql.com
It installed very clean and easy.
When I launch it, it opens as expected.
I can connect to mysql server on localhost as root and as myself (larry).
Every query I have tried immediately crashes the app.
There are no warning messages, no errors logged in
~/Library/Application Support/MySQL/Workbench/log/
wb.log contains only [INF] and [WRN] messages.
% cat sql_actions_Local_instance_3306.log
[1, 17:01:52] SHOW DATABASES: Running...
[1, 17:01:52] SHOW DATABASES: Fetching...
[1, 17:01:52] SHOW DATABASES: 4 row(s) returned
[1, 17:07:47] Use mysql: Running...
[1, 17:07:47] Use mysql: 0 row(s) affected
[2, 17:08:06] Use mysql: Running...
[2, 17:08:06] Use mysql: 0 row(s) affected
[3, 17:08:06] SHOW TABLES: Running...
[3, 17:08:06] SHOW TABLES: Fetching...
[3, 17:08:06] SHOW TABLES: 37 row(s) returned
The "use mysql" did not cause a crash.
The only thing I can say for sure is that querys that require a result crash the application.
Perhaps, this information will be helpful:
17:07:33 [INF][ WBContext]: System info:
MySQL Workbench Community (GPL) for macOS version 8.0.32 CE build 2612062 (64 bit)
Configuration Directory: /Users/larry/Library/Application Support/MySQL/Workbench
Data Directory: /Applications/MySQLWorkbench.app/Contents/Resources
Cairo Version: 1.17.6
OS: unknown
CPU: 20x Intel(R) Xeon(R) W-2150B CPU @ 3.00GHz - 128.00GiB RAM
No video adapter info available
Please note, I previously installed MySQL Workbench 8.0.32 from Homebrew.
I uninstalled it and purged the log files. Any idea why software from
dev.mysql.com would have this in wb.log?
17:07:35 [INF][SQL Editor Form]: Opened connection 'Local instance 3306' to Homebrew version 8.0.32
How to repeat:
It is consistent. Any query that would generate output crashed the application without any indication there is a problem.
Suggested fix:
I have no idea how to fix this.
Please let me know if I can provide more information.
In Mac console app I find crash reports. They are huge.
All they say is "illegal instruction" caused the crash.
But, not what the instruction was.
The backtrace is so deep it is impossible for me to narrow down cause.
Description: I downloaded mysql-workbench-community-8.0.32-macos-x86_64.dmg from dev.mysql.com It installed very clean and easy. When I launch it, it opens as expected. I can connect to mysql server on localhost as root and as myself (larry). Every query I have tried immediately crashes the app. There are no warning messages, no errors logged in ~/Library/Application Support/MySQL/Workbench/log/ wb.log contains only [INF] and [WRN] messages. % cat sql_actions_Local_instance_3306.log [1, 17:01:52] SHOW DATABASES: Running... [1, 17:01:52] SHOW DATABASES: Fetching... [1, 17:01:52] SHOW DATABASES: 4 row(s) returned [1, 17:07:47] Use mysql: Running... [1, 17:07:47] Use mysql: 0 row(s) affected [2, 17:08:06] Use mysql: Running... [2, 17:08:06] Use mysql: 0 row(s) affected [3, 17:08:06] SHOW TABLES: Running... [3, 17:08:06] SHOW TABLES: Fetching... [3, 17:08:06] SHOW TABLES: 37 row(s) returned The "use mysql" did not cause a crash. The only thing I can say for sure is that querys that require a result crash the application. Perhaps, this information will be helpful: 17:07:33 [INF][ WBContext]: System info: MySQL Workbench Community (GPL) for macOS version 8.0.32 CE build 2612062 (64 bit) Configuration Directory: /Users/larry/Library/Application Support/MySQL/Workbench Data Directory: /Applications/MySQLWorkbench.app/Contents/Resources Cairo Version: 1.17.6 OS: unknown CPU: 20x Intel(R) Xeon(R) W-2150B CPU @ 3.00GHz - 128.00GiB RAM No video adapter info available Please note, I previously installed MySQL Workbench 8.0.32 from Homebrew. I uninstalled it and purged the log files. Any idea why software from dev.mysql.com would have this in wb.log? 17:07:35 [INF][SQL Editor Form]: Opened connection 'Local instance 3306' to Homebrew version 8.0.32 How to repeat: It is consistent. Any query that would generate output crashed the application without any indication there is a problem. Suggested fix: I have no idea how to fix this. Please let me know if I can provide more information. In Mac console app I find crash reports. They are huge. All they say is "illegal instruction" caused the crash. But, not what the instruction was. The backtrace is so deep it is impossible for me to narrow down cause.