Re: MySQLWorkbench quit unexpectedly crashes

[Orin Eman]

That's a somewhat different error - SIGSEGV rather than SIGILL...

The underlying cause is likely the same though - a bad pointer causing it to execute random code. Memory use after free and it crashes if the memory has been reused would be my guess.

FWIW, the downgrade to 8.0.29 did work for me.

Orin.

Andrés Mojica Ospina Wrote:
-------------------------------------------------------
> Hi,
>
> I tried the solution proposed by Matt, however i
> still have the same error message:
>
> -------------------------------------
> Translated Report (Full Report Below)
> -------------------------------------
>
> Process: MySQLWorkbench [3644]
> 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: 2023-01-20 13:43:21.9039
> -0500
> OS Version: macOS 13.1 (22C65)
> Report Version: 12
> Bridge OS Version: 7.1 (20P2059)
> Anonymous UUID:
> 50199FF2-3D40-CDB3-CC7A-273A909E1966
>
>
> Time Awake Since Boot: 2200 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