mysterious crashes Max 8 on Mac OS 15.1
got some unexpected and poorly timed crashes during live performance with no clues as to what went wrong.
main question is if anyone has advice on how to read these .ips reports generated by the crash -- just pasting the first chunk below, any tips on how to track down the culprit based off this or what keywords to look for would be greatly appreciated.
///
Process: Max [414]
Path: /Applications/Max.app/Contents/MacOS/Max
Identifier: com.cycling74.Max
Version: 8.6.5 (795b32eda25) (8.6.5)
Code Type: ARM-64 (Native)
Parent Process: launchd [1]
User ID: 501
Date/Time: 2025-02-28 19:00:05.7503 -0800
OS Version: macOS 15.1 (24B2083)
Report Version: 12
Anonymous UUID: 013C5E49-6637-9D67-C624-071AF6F59577
Time Awake Since Boot: 980 seconds
System Integrity Protection: enabled
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process: Max [414]
Application Specific Information:
abort() called
Kernel Triage:
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
VM - (arg = 0x3) mach_vm_allocate_kernel failed within call to vm_map_enter
Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x190092600 __pthread_kill + 8
1 libsystem_pthread.dylib 0x1900caf70 pthread_kill + 288
2 libsystem_c.dylib 0x18ffd7908 abort + 128
3 libsystem_malloc.dylib 0x18fee1524 malloc_vreport + 896
4 libsystem_malloc.dylib 0x18fee50a8 malloc_report + 64
5 libsystem_malloc.dylib 0x18ff031a4 find_zone_and_free + 528
6 libsystem_malloc.dylib 0x18ff033d8 _realloc + 208
7 mira.frame 0x13613cc0c XEBStateUpdateListener_HandleOSCMessage + 288
8 mira.frame 0x13613ce94 XEBStateUpdateListener_HandleModifiedNode + 152
9 mira.frame 0x13613e1c8 XEBState_NotifyRemoteNoLock + 320
10 mira.frame 0x13613e050 XEBState_NotifyParam + 120
11 mira.frame 0x13612c160 XEBNotifyObjectParamHelper + 220
12 mira.frame 0x13612b9b0 XEBNotifyObjectParamMaybeIgnore + 164
13 mira.frame 0x13612ac08 xebra_global_notify + 2112
14 Max 0x1043457e0 linklist_methodall_imp + 340
15 Max 0x104342e54 object_notify + 408
16 number 0x109e74ac4 jflonum_assign + 136
17 number 0x109e6f4d8 jnumber_float + 40
18 Max 0x10434b790 outlet_float + 1408
19 Max 0x10434b790 outlet_float + 1408
20 Max 0x104354310 linklist_funall_imp + 376
21 Max 0x10445d170 through_scheduler_sendit_extended + 144
22 Max 0x104458f68 send_float + 100
23 Max 0x10434b790 outlet_float + 1408
24 Max 0x10434b790 outlet_float + 1408
25 Max 0x1044574b4 route_anything + 288
26 Max 0x10434d7f8 typedmess_fun + 224
27 Max 0x104337780 outlet_anything + 1500
28 Max 0x1043671e8 object_attr_getdump + 196
29 Max 0x10434d7f8 typedmess_fun + 224
30 Max 0x104337780 outlet_anything + 1500
31 Max 0x10445deb4 trigger_iterate + 244
32 Max 0x10434d7f8 typedmess_fun + 224
33 Max 0x104337780 outlet_anything + 1500
34 jit.world 0x3ed880fc4 max_jit_world_draw + 544
35 Max 0x10437f614 sched_dequeue + 372
36 Max 0x1041b05e0 MainThreadEventHandler::invoke() + 88
37 Max 0x1046c4968 juce::Timer::TimerThread::callTimers() + 344
38 Max 0x1046c5a04 juce::MessageQueue::runLoopCallback() + 64
39 CoreFoundation 0x1901b1d34 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
40 CoreFoundation 0x1901b1cc8 __CFRunLoopDoSource0 + 176
41 CoreFoundation 0x1901b1a2c __CFRunLoopDoSources0 + 244
42 CoreFoundation 0x1901b05c8 __CFRunLoopRun + 840
43 CoreFoundation 0x1901afbc4 CFRunLoopRunSpecific + 588
44 HIToolbox 0x19b621f64 RunCurrentEventLoopInMode + 292
45 HIToolbox 0x19b627d54 ReceiveNextEventCommon + 636
46 HIToolbox 0x19b627eb8 _BlockUntilNextEventMatchingListInModeWithFilter + 76
47 AppKit 0x193cdb98c _DPSNextEvent + 660
48 AppKit 0x19461bddc -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
49 AppKit 0x193ccea64 -[NSApplication run] + 480
50 Chromium Embedded Framework 0x11e9ec874 ChromeAppModeStart_v7 + 6667352
51 Chromium Embedded Framework 0x11e9eaf30 ChromeAppModeStart_v7 + 6660884
52 Chromium Embedded Framework 0x11e9989d0 ChromeAppModeStart_v7 + 6323636
53 Chromium Embedded Framework 0x11e96372c ChromeAppModeStart_v7 + 6105872
54 Chromium Embedded Framework 0x11b7300a0 cef_zip_reader_create + 392124
55 Max 0x104021d0c MaxCefEventLoopHandler::runMessageLoop() + 28
56 Max 0x1046bfcd0 juce::JUCEApplicationBase::main() + 192
57 Max 0x1046bfbf0 juce::JUCEApplicationBase::main(int, char const**) + 88
58 dyld 0x18fd48274 start + 2840
This looks like a crash in mira.frame while trying to reallocate memory for an OSC message. It could be general memory corruption, or some issues with multi-threading, or some other bug. If you are able to create a reproducible example patch that can demonstrate this problem, we'd be happy to investigate further.
Hey thanks so much Joshua for the reply, and for the tip re: Mira.
I appreciate the willingness to debug the patch, however I reckon replicating the crash would be pretty much impossible. It is a performance patch I run continuously for ~45 min straight in a sequenced progression and is comprised of many sub-patchers all doing different things (sample playback with poly~ and groove~, MIDI sequencing sent out to Live, custom synths, etc. -- not to mention live video processing/mixing with jitter and vsynth).
The crash happened about 10 min in to my set at a moment that was seemingly non-intensive for the CPU and/or GPU. I am intrigued by the Mira hypothesis because I had just that day added a new tab to Mira (making four up from three), which was the only new structural change to the patch as a whole before the crash.
Not at all sure it's helpful but I've uploaded the Mira sub-patcher just in case there's anything I'm missing. It's almost all sends and receives to other sub-patchers but who knows. I did hear that Mira has been on the back burner for some time now so maybe it's time to move on from it? FWIW I had it connected over USB, not WiFi.