MySQL Bugs: #112440: On MacOS 14 Sonoma system,The App crashes every time I open a model

Bug #112440	On MacOS 14 Sonoma system,The App crashes every time I open a model
Submitted:	23 Sep 2023 4:03	Modified:	4 Jan 21:30
Reporter:	YP Li	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Workbench: Modeling	Severity:	S3 (Non-critical)
Version:	8.0.34, 8.0.26	OS:	MacOS (14 Sonoma)
Assigned to:	Marcin Marek	CPU Architecture:	ARM (Apple M2)
Tags:	crash, modeling, sonoma, workbench

Description:
On MacOS 14 Sonoma system,The App crashes every time I open a model

How to repeat:
On MacOS 14 Sonoma system,The App crashes every time I open a model

Bug #112442 marked as duplicate of this one.

Hello!

Thank you for the bug report.
Please note that MacOS 14 is not yet supported by MySQL Workbench.
For more info please see here https://www.mysql.com/support/supportedplatforms/database.html

Regards,
Ashwini Patil

Bug #112533 marked as duplicate of this one.

Bug #112536 marked as duplicate of this one.

Bug #112547 marked as duplicate of this one.

Bug #112565 marked as duplicate of this one.

Bug #112573 marked as duplicate of this one.

Bug #112578 marked as duplicate of this one.

Bug #112610 marked as duplicate of this one.

Bug #112624 marked as duplicate of this one.

Bug #112638 marked as duplicate of this one.

Bug #112637 marked as duplicate of this one.

Bug #112652 marked as duplicate of this one.

Bug #112658 marked as duplicate of this one.

Bug #112671 marked as duplicate of this one.

Bug #112706 marked as duplicate of this one.

Bug #112709 marked as duplicate of this one.

When will this bug be fixed?

Bug #112721 marked as duplicate of this one.

Bug #112730 marked as duplicate of this one.

Bug #112725 marked as duplicate of this one.

Bug #112716 marked as duplicate of this one.

Bug #112753 marked as duplicate of this one.

Bug #112756 marked as duplicate of this one.

Error_message_M1

Attachment:  error_message_M1.rtf (text/rtf), 82.18 KiB.

Several MAC`s here where I work present unexpected closing of MySQLWorkkbench, both for ARM and Intel.

I have created a patch to address inaccurate data processing, which seems to be the cause of the crash. This patch might prevent the app from crashing.

It appears that setting autosaveName before restoreSidebarsFor causes splitViewDidResizeSubviews to be called first, thus accessing the NULL pointer.

diff --git a/frontend/mac/workbench/WBModelDiagramPanel.mm b/frontend/mac/workbench/WBModelDiagramPanel.mm
index bc52b5d7c..357144636 100644
--- a/frontend/mac/workbench/WBModelDiagramPanel.mm
+++ b/frontend/mac/workbench/WBModelDiagramPanel.mm
@@ -149,8 +149,6 @@ static void *backend_destroyed(void *ptr) {
 
       [self setRightSidebar: be->get_wb()->get_wb_options().get_int("Sidebar:RightAligned", 0)];
 
-      self.splitView.autosaveName = @"diagramSplitPosition";
-
       mSwitcherT.tabStyle = MSectionTabSwitcher;
       mSwitcherM.tabStyle = MSectionTabSwitcher;
       mSwitcherB.tabStyle = MSectionTabSwitcher;
@@ -178,6 +176,8 @@ static void *backend_destroyed(void *ptr) {
       }
       
       [self restoreSidebarsFor: "ModelDiagram" toolbar: _formBE->get_toolbar()];
+
+      self.splitView.autosaveName = @"diagramSplitPosition";
     }
   }
   return self;
diff --git a/frontend/mac/workbench/WBModelOverviewPanel.mm b/frontend/mac/workbench/WBModelOverviewPanel.mm
index 8cfd5ac39..68e53d1ef 100644
--- a/frontend/mac/workbench/WBModelOverviewPanel.mm
+++ b/frontend/mac/workbench/WBModelOverviewPanel.mm
@@ -72,9 +72,10 @@
 
       [overview performSelector: @selector(rebuildAll) withObject: nil afterDelay: 0.1];
 
+      [self restoreSidebarsFor: "ModelOverview" toolbar: wb::WBContextUI::get()->get_physical_overview()->get_toolbar()];
+
       self.splitView.autosaveName = @"modelSplitPosition";
 
-      [self restoreSidebarsFor: "ModelOverview" toolbar: wb::WBContextUI::get()->get_physical_overview()->get_toolbar()];
     }
   }

Hi Yasushi
Where to add this code/patch? 

Thanks
Christo

Bug #112789 marked as duplicate of this one.

Bug #112791 marked as duplicate of this one.

Bug #112793 marked as duplicate of this one.

Bug #112797 marked as duplicate of this one.

Hello, i also having this issue, when mysql workbench can work on sonoma 14?

Is it possible to provide the built app for the patch? I need it for school

The patch above only stopped crashing, the UI was broken.

Now that 8.0.35 has been added to the Release Notes page, I am hopeful that a supported version will be released soon.

Bug #112878 marked as duplicate of this one.

Bug #112875 marked as duplicate of this one.

Bug #112810 marked as duplicate of this one.

Bug #112939 marked as duplicate of this one.

Why is this closed as Unsupported? It should be kept reopened until the new release is GA and/or fixVersion is set.
Unsupported means it's never going to be supported, while obviously in this case it doesn't apply.

Bug #112956 marked as duplicate of this one.

Bug #113074 marked as duplicate of this one.

Bug #113081 marked as duplicate of this one.

Bug #113082 marked as duplicate of this one.

Bug #113083 marked as duplicate of this one.

Bug #113085 marked as duplicate of this one.

Bug #113101 marked as duplicate of this one.

Bug #113128 marked as duplicate of this one.

Bug #113133 marked as duplicate of this one.

Bug #113157 marked as duplicate of this one.

Bug #113195 marked as duplicate of this one.

Bug #113204 marked as duplicate of this one.

Bug #113223 marked as duplicate of this one.

Bug #113220 marked as duplicate of this one.

Bug #113221 marked as duplicate of this one.

Bug #113224 marked as duplicate of this one.

Why is the severity S3? It should be S1. Workbench can't be used anymore.

Please fix this with high priority, can't edit my models anymore ..
Should be S1

Bug #113238 marked as duplicate of this one.

I agree, severity is incorrect, it should be 1.  we rely heavily on models and it has hindered development

Any idea when MacOS 14 will be supported?

Bug #113297 marked as duplicate of this one.

It's been more than 2 months since this was reported. The SW is practically unusable in MacOS Sonoma, which was released back in September. Downgrading to a previous O.S. version just because of this is not easy and a lot of people depend on MySQLWorkbench for comparable productivity. There aren't even valid workarounds.
Why can't Oracle release a patch to fix this yet?

It's been 2 months and they still haven't resolved it. It's a sad situation.

Bug #113314 marked as duplicate of this one.

The answer that MacOS 14 is not supported is no longer the case according to the reference cited: https://www.mysql.com/support/supportedplatforms/database.html

Is this bug scheduled with the Mac support team yet?  

Thank you

This is the correct link: https://www.mysql.com/support/supportedplatforms/workbench.html

Bug #113372 marked as duplicate of this one.

As macos sonoma is released, Workbench should be supported macOS 14 x86_64 and arm64. The severity of the bug should be S1 (Critical).

Make sure you have all set the "Impact on Me" option at the top to help prioritise this issue. It is an S1 if you have updated to Sonoma. I am having to wait along with a number of development teams on the old OS.

Bug #113412 marked as duplicate of this one.

Please reopen this bug. Tool is unusable and is very useful!

confirmed, i fixed changes made in macOs 14 cocoa framework

Hello, Marcin Marek 

I'm so glad you were able to fix this. It's awesome.

Sincerely,
Pattarachai Srilaporn

Great Marcin Marek; will there be a new release soon?

Hi Marcin,

Please, let us know when the fix will be available. Many of us will appreciate it. Do we have to wait for the 8.0.35 release or will there be a patch/nightly version available?

Thank you so much!

Realy nice that all duplicates point to this ticket, but how on earth can the severity of this ticket be S3 (Non-critical) ?!

The product is unusable since September?!

Bug #113504 marked as duplicate of this one.

Posted by developer:
 
Fixed as of the upcoming MySQL Workbench 8.0.36 release, and here's the proposed changelog entry from the documentation team:

On macOS 14, MySQL Workbench would unexpectedly halt when attempting to
open a model.

Thank you for the bug report.

Bug #113589 marked as duplicate of this one.

Any idea when 8.0.36 will be released?

Has version 8.0.35 been skipped?

I would like te remart that the issue is any CPU architecture also x86.

Can someone please give an indication on the timeline for 8.0.36 !?

[10 Jan 19:59] Donovan Torgerson

"Any idea when 8.0.36 will be released?"

See my answer below.

[11 Jan 11:10] Lodewijk Duymaer van Twist

"Has version 8.0.35 been skipped?"

It seems so.

"Can someone please give an indication on the timeline for 8.0.36 !?"

As the timeline for Oracle's this year's 2024 Critical Patch Updates outlines on https://www.oracle.com/security-alerts/ and todays Pre-Release Announcement for the pending next one on
https://www.oracle.com/security-alerts/cpujan2024.html
https://www.oracle.com/security-alerts/cpujan2024.html#AppendixMSQL
I guess and hope: in a few days on 16 January 2024.
Maybe someone of the MySQL Verification Team would be so kind to confirm or deny.

Bug #113636 marked as duplicate of this one.

I had been experiencing this issue and stumbled on this thread yesterday, downloaded the fresh 8.0.36, and can confirm that it no longer crashes when opening an ERD file or creating new diagrams. However, it appears elements of the GUI are failing silently; Specifically, I noticed the label for a table name input and the text input aren't visible. I cannot see the text I am editing in that field. Assuming this new problem affects the same people, any energy on this bug fix should be redirected to Bug#113660. https://bugs.mysql.com/bug.php?id=113660

Agree with Coren Frankel when use 8.0.36 GA. Table name should be displayed for editing in the tab.

Bug #113692 marked as duplicate of this one.

Bug #114025 marked as duplicate of this one

Bug #114417 marked as duplicate of this one

I'm still encountering a crash on Sonoma 14.4.1 and MySQL Workbench 8.0.28 on my M1 Mac mini when I try and run a query. Not every time but frequently enough to make the tool unusable. Here's the head of the problem report:

Notes:
PC register does not match crashing frame (0x0 vs 0x10C8DFA1B)

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

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0xb00007f97a82e320 -> 0x000007f97a82e320 (possible pointer authentication failure)
Exception Codes:       0x0000000000000001, 0xb00007f97a82e320

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

VM Region Info: 0x7f97a82e320 is not in any region.  Bytes after previous region: 8287047312161  Bytes before following region: 96785032617184
      REGION TYPE                    START - END         [ VSIZE] PRT/MAX SHRMOD  REGION DETAIL
      commpage (reserved)        1000000000-7000000000   [384.0G] ---/--- SM=NUL  reserved VM address space (unallocated)
--->  GAP OF 0x5f9000000000 BYTES
      MALLOC_NANO              600000000000-600020000000 [512.0M] rw-/rwx SM=PRV  

Error Formulating Crash Report:
PC register does not match crashing frame (0x0 vs 0x10C8DFA1B)