Bug #108527 MYSQL workbench quit unexpectedly after install
Submitted: 18 Sep 2022 5:25 Modified: 19 Oct 2022 13:03
Reporter: Jirakit Paitoonnaramit Email Updates:
Status: No Feedback Impact on me:
None 
Category:MySQL Workbench Severity:S1 (Critical)
Version:8.0.30 OS:MacOS (12.6)
Assigned to: MySQL Verification Team CPU Architecture:x86

[18 Sep 2022 5:25] Jirakit Paitoonnaramit
Description:
I just change version from 8.0.23 to  8.0.30 and it show MYSQL workbench quit unexpectedly after install after that I roll back to 8.0.23 and it also show MYSQL workbench quit unexpectedly !!

This is my bug report.

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               MySQLWorkbench [12464]
Path:                  /Volumes/VOLUME/MySQLWorkbench.app/Contents/MacOS/MySQLWorkbench
Identifier:            com.oracle.workbench.MySQLWorkbench
Version:               8.0.30.CE (1)
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               501

Date/Time:             2022-09-18 12:23:57.0735 +0700
OS Version:            macOS 12.6 (21G115)
Report Version:        12
Anonymous UUID:        93C12037-7AA4-2F17-6953-BD95C09A967C

Sleep/Wake UUID:       849BC91A-1470-44CE-9BD7-E5AD32B72263

Time Awake Since Boot: 10000 seconds
Time Since Wake:       1282 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Codes:       0x0000000000000001, 0x0000000000000008
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process:   exc handler [12464]

How to repeat:
1. Download the installer.
2. Run program.
3. The error is shown.
[18 Sep 2022 5:42] Jirakit Paitoonnaramit
Full bug report

Attachment: full (application/octet-stream, text), 27.01 KiB.

[19 Sep 2022 13:03] MySQL Verification Team
Hello,

Thank you for the bug report.
To investigate further this issue at our end, may I kindly request you to launch workbench under debug mode (--log-level=debug3) and provide unaltered workbench log file(more details about log are explained here - https://dev.mysql.com/doc/workbench/en/workbench-reporting-bugs.html)? Thanks.

Regards,
Ashwini Patil
[20 Oct 2022 1:00] Bugs System
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".