Bug #112789 Workbench diagrams crashes on every version on MacOs Sonoma

Description:
If I create a new diagram or open an existing mwb file, it crashes with the next log:

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

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

Date/Time: 2023-09-27 13:31:42.8268 +0200
OS Version: macOS 14.0 (23A344)
Report Version: 12
Anonymous UUID: D1432EEE-51EB-13EA-828B-17B4246D95E4

Sleep/Wake UUID: C359E3B4-2B74-45F5-A41A-7A08A02CC316

Time Awake Since Boot: 14000 seconds
Time Since Wake: 6548 seconds

System Integrity Protection: disabled

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000000000e0
Exception Codes: 0x0000000000000001, 0x00000000000000e0

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

VM Region Info: 0xe0 is not in any region. Bytes before following region: 4309352224
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
--->
__TEXT 100db8000-100e0c000 [ 336K] r-x/r-x SM=COW ...ySQLWorkbench

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libmforms.dylib 0x102a80098 mforms::ToolBar::find_item(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) + 28
1 libmforms.dylib 0x102a80344 mforms::ToolBar::get_item_checked(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char>> const&) + 12
2 WBExtras 0x10188ba50 -[WBSidebarPanel splitViewDidResizeSubviews:] + 360
3 CoreFoundation 0x1835e4780 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148
4 CoreFoundation 0x1836789a8 ___CFXRegistrationPost_block_invoke + 88

How to repeat:
Creating a new diagram or getting the reverse engineer of DB

Hello!

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

Regards,
Ashwini Patil