cancel
Showing results for 
Search instead for 
Did you mean: 

STM32CubeIDE crashes on MacOS Ventura 13.0.1

ron239955_stm1
Associate III

I just upgraded to MacOX Ventura 13.0.1 from MacOS 12 last night, and now STM32CubeIDE 1.10.1 crashes about 8 1/2 minutes from app startup, consistently. This is on a 2019 Intel 16" MacBook Pro. The crash happens even if the app is left idle.

Has anyone else experienced this? Any suggestions on how to fix this?

Here's part of the crash dump. I can post everything if needed.

-------------------------------------

Translated Report (Full Report Below)

-------------------------------------

Process:       stm32cubeide [12688]

Path:         /Applications/STM32CubeIDE.app/Contents/MacOS/STM32CubeIDE

Identifier:      stm32cubeide

Version:       ???

Code Type:      X86-64 (Native)

Parent Process:    launchd [1]

User ID:       502

Date/Time:      2022-11-21 11:54:25.8404 -0800

OS Version:      macOS 13.0.1 (22A400)

Report Version:    12

Bridge OS Version:  7.0 (20P420)

Anonymous UUID:    F885FB99-C439-51DC-FB8A-19B44CFBD64C

Sleep/Wake UUID:   C17EA655-41B9-4F6C-9120-60DD4299EA39

Time Awake Since Boot: 37000 seconds

Time Since Wake:   6199 seconds

System Integrity Protection: enabled

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

Exception Type:    EXC_BAD_ACCESS (SIGABRT)

Exception Codes:   UNKNOWN_0xD at 0x0000000000000000

Exception Codes:   0x000000000000000d, 0x0000000000000000

VM Region Info: 0 is not in any region. Bytes before following region: 211800064

   REGION TYPE          START - END    [ VSIZE] PRT/MAX SHRMOD REGION DETAIL

   UNUSED SPACE AT START

---> 

   __TEXT            c9fd000-ca01000   [ 16K] r-x/r-x SM=COW .../stm32cubeide

Application Specific Information:

abort() called

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

0 libsystem_kernel.dylib       0x7ff80ea9530e __pthread_kill + 10

1 libsystem_pthread.dylib      0x7ff80eaccf7b pthread_kill + 263

2 libsystem_c.dylib         0x7ff80ea16ca5 abort + 123

3 libjvm.dylib              0x198c7914 os::abort(bool, void*, void const*) + 22

4 libjvm.dylib              0x19a63fdc VMError::report_and_die(int, char const*, char const*, __va_list_tag*, Thread*, unsigned char*, void*, void*, char const*, int, unsigned long) + 2858

5 libjvm.dylib              0x19a6348d VMError::report_and_die(Thread*, unsigned int, unsigned char*, void*, void*, char const*, ...) + 155

6 libjvm.dylib              0x19a6412d VMError::report_and_die(Thread*, unsigned int, unsigned char*, void*, void*) + 33

7 libjvm.dylib              0x198cb6d3 JVM_handle_bsd_signal + 544

8 libjvm.dylib              0x198c92db signalHandler(int, __siginfo*, void*) + 45

9 libsystem_platform.dylib      0x7ff80eaf7c1d _sigtramp + 29

10 JavaScriptCore           0x7ff829246849 JSC::ExecutableAllocator::allocate(unsigned long, JSC::JITCompilationEffort) + 249

11 JavaScriptCore           0x7ff828a8f027 vmEntryToJavaScript + 216

12 JavaScriptCore           0x7ff829230161 JSC::Interpreter::executeCall(JSC::JSGlobalObject*, JSC::JSObject*, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&) + 545

13 JavaScriptCore           0x7ff8294985cb JSC::profiledCall(JSC::JSGlobalObject*, JSC::ProfilingReason, JSC::JSValue, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&, WTF::NakedPtr<JSC::Exception>&) + 107

14 WebCore              0x7ff82cf0dc0b WebCore::JSExecState::profiledCall(JSC::JSGlobalObject*, JSC::ProfilingReason, JSC::JSValue, JSC::CallData const&, JSC::JSValue, JSC::ArgList const&, WTF::NakedPtr<JSC::Exception>&) + 107

15 WebCore              0x7ff82cf4d0ba WebCore::ScheduledAction::executeFunctionInContext(JSC::JSGlobalObject*, JSC::JSValue, WebCore::ScriptExecutionContext&) + 282

16 WebCore              0x7ff82cf4cdb2 WebCore::ScheduledAction::execute(WebCore::Document&) + 194

17 WebCore              0x7ff82bf0a75e WebCore::DOMTimer::fired() + 1614

18 WebCore              0x7ff82d950f48 WTF::Detail::CallableWrapper<WebCore::ThreadTimers::setSharedTimer(WebCore::SharedTimer*)::$_0, void>::call() + 152

19 WebCore              0x7ff82be3974f WebCore::timerFired(__CFRunLoopTimer*, void*) + 31

20 CoreFoundation           0x7ff80ebc0996 __CFRUNLOOP_IS_CALLING_OUT_TO_A_TIMER_CALLBACK_FUNCTION__ + 20

21 CoreFoundation           0x7ff80ebc04fe __CFRunLoopDoTimer + 820

22 CoreFoundation           0x7ff80ebc0114 __CFRunLoopDoTimers + 285

23 CoreFoundation           0x7ff80eba6a5c __CFRunLoopRun + 2098

24 CoreFoundation           0x7ff80eba5bb0 CFRunLoopRunSpecific + 560

25 Foundation             0x7ff80f9fe49a -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 216

26 libswt-pi-cocoa-4950r5.jnilib     0x39319b29 Java_org_eclipse_swt_internal_cocoa_OS_objc_1msgSend_1bool__JJJJ + 57

27 ???                  0x2b300c87 ???

28 ???                  0x2b8e5d2c ???

1 ACCEPTED SOLUTION

Accepted Solutions
Julien D
ST Employee

I confirm that I could reproduce this crash by keeping the application opened displaying the WelcomePage during several minutes.

If I let STM32CubeIDE running after having closed the WelcomePage then I don't reproduce the crash, at least after 30min...

This would be coherent with the crash dump, claiming for an issue in JavaScriptCore, because the only place where the IDE exercices JavaScript is the WelcomePage.

Can you confirm this behavior on your side too?

In the meantime I log an internal ticket, thanks for the report.

View solution in original post

5 REPLIES 5
Julien D
ST Employee

I confirm that I could reproduce this crash by keeping the application opened displaying the WelcomePage during several minutes.

If I let STM32CubeIDE running after having closed the WelcomePage then I don't reproduce the crash, at least after 30min...

This would be coherent with the crash dump, claiming for an issue in JavaScriptCore, because the only place where the IDE exercices JavaScript is the WelcomePage.

Can you confirm this behavior on your side too?

In the meantime I log an internal ticket, thanks for the report.

Rim LANDOLSI
ST Employee

Hello ron239955_stm1 ,

Thank you for posting your problem.

Could you please delete log files of your workspace (.metdata/.log and .metdata/.ide.log ) ,then louch CubeIDE tool and keep it until it craches to see what happens in the logs at this moment.

Best regards ,

Rim

Ok, here are the files.

And the other one...

I can confirm this - I closed the welcome page, and it's been running for a few hours now.

Thanks for the quick response and the helpful suggestion!