Bug #115170 Mysql Workbench continuously crashes. Also I have schema call tradeDB crashes

Submitted:	30 May 2024 1:44	Modified:	30 May 2024 12:23
Reporter:	Andrew Berman	Email Updates:
Status:	Duplicate	Impact on me:	None
Category:	MySQL Workbench	Severity:	S3 (Non-critical)
Version:	8.0.29.CE	OS:	MacOS (Sonoma 14.4.1)
Assigned to:		CPU Architecture:	x86

Description:
Translated Report (Full Report Below)
-------------------------------------

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

Date/Time:             2024-05-29 18:02:38.3862 -0700
OS Version:            macOS 14.4.1 (23E224)
Report Version:        12
Bridge OS Version:     8.4 (21P4222)
Anonymous UUID:        0039ACFB-2350-57C8-B651-1F6A7862F1CC

Sleep/Wake UUID:       A492662C-0DD5-446B-AEBD-735A2B5618BA

Time Awake Since Boot: 94000 seconds
Time Since Wake:       38571 seconds

System Integrity Protection: enabled

Crashed Thread:        11  Dispatch queue: CA DispatchGroup

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       UNKNOWN_0xD at 0x0000000000000000
Exception Codes:       0x000000000000000d, 0x0000000000000000

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

How to repeat:
it continuous happens on random basis.

Hello Andrew Berman,

Thank you for the bug report.
Imho this is duplicate of Bug #109671, please see Bug #109671.

Regards,
Ashwini Patil

Page generated in 0.052 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.