Ableton Crashed during show

Support
1

Describe your issue here:

Hi all, I just had a show on Saturday and Ableton crashed in the middle of it. Ableton log does not show anything and I can’t read the crash report from Ableton, but i sent it to support. But since people here are really quick I thought I might have a better chance of help here. On the MacOS Console I found another crash report:

Thread 0 Crashed:: MainThread Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	       0x184541388 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x18457a88c pthread_kill + 296
2   libsystem_c.dylib             	       0x184483c60 abort + 124
3   libsystem_malloc.dylib        	       0x184388174 malloc_vreport + 892
4   libsystem_malloc.dylib        	       0x1843b3a00 malloc_zone_error + 100
5   libsystem_malloc.dylib        	       0x1843a1540 nanov2_guard_corruption_detected + 44
6   libsystem_malloc.dylib        	       0x1843a150c nanov2_allocate_outlined + 460
7   libsystem_malloc.dylib        	       0x1843a0260 nanov2_calloc_type + 568
8   CoreFoundation                	       0x18462bc2c __NSSetM_new + 232
9   CoreFoundation                	       0x18467d5a8 +[NSMutableSet setWithCapacity:] + 32
10  AppKit                        	       0x1885a20e8 -[NSDisplayCycle addObserver:] + 240
11  AppKit                        	       0x188fee02c -[NSWindow(NSDisplayCycle) _postWindowNeedsDisplay] + 1628
12  AppKit                        	       0x1890a8d50 NSViewSetNeedsUpdateVibrancy + 52
13  AppKit                        	       0x1885a3e10 -[NSView setNeedsDisplayInRect:] + 296
14  Live                          	       0x105994af0 0x1042c0000 + 23939824
15  Live                          	       0x105994b44 0x1042c0000 + 23939908
16  Live                          	       0x105a646b8 0x1042c0000 + 24790712
17  Live                          	       0x105a64e34 0x1042c0000 + 24792628
18  Live                          	       0x10597f800 0x1042c0000 + 23853056
19  Live                          	       0x10597e720 0x1042c0000 + 23848736
20  Live                          	       0x1059783d4 0x1042c0000 + 23823316
21  Live                          	       0x105978384 0x1042c0000 + 23823236
22  CoreFoundation                	       0x184665874 __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 28
23  CoreFoundation                	       0x184665784 __CFRunLoopDoBlocks + 352
24  CoreFoundation                	       0x184664c30 __CFRunLoopRun + 2384
25  CoreFoundation                	       0x184663c58 CFRunLoopRunSpecific + 572
26  HIToolbox                     	       0x1900f827c RunCurrentEventLoopInMode + 324
27  HIToolbox                     	       0x1900fb4e8 ReceiveNextEventCommon + 676
28  HIToolbox                     	       0x190286484 _BlockUntilNextEventMatchingListInModeWithFilter + 76
29  AppKit                        	       0x18858bab4 _DPSNextEvent + 684
30  AppKit                        	       0x188f2a5b0 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
31  AppKit                        	       0x18857ec64 -[NSApplication run] + 480
32  Live                          	       0x10597ad50 0x1042c0000 + 23833936
33  dyld                          	       0x1841dab98 start + 6076

I adon’t really understand what went wrong, but I saw that one of the last things it did was Mute Ableset. Can anybody read this report and tell me what happened?

I updated live recently from 12.3.4 to 12.4.2, I don’t know if I should roll back.

Please fill out these values to make it easier to troubleshoot:

  • OS and Version: Sequoia 15.5
  • Version of AbleSet: 3.0.11
  • Version of Ableton Live: 12.4.2
2

Unfortunately, this doesn’t give us a ton of information. What we can see is that the crash was caused by some kind of memory error, triggered by something in the GUI. This could be caused by any number of things, including third-party plugins. Not much else can be gathered from these logs, but maybe Ableton support will be able to identify issues from the more detailed Live 12 logs.

3

hey @s1ah , thanks for your insights. I did not have any plugin windows open during the show. So if it’s a GUI problem I’d guess it has to do with ableton itself. Let’s hope they will respond soon.

4

@leolabs ableton just replied to my request and told me Ableton crashed while trying to redraw the gui because of a memory error. but we can’t really tell why it happened.

But he also saw, that ableset is logging “multiple delayed UDP-cycles” during start up. I don’t know really what that means, but maybe worth looking into?

5

Hey @FAster77, the UDP-related log messages usually show up when AbleSet’s plugin isn’t able to listen to incoming commands regularly enough. This can happen if Live’s main thread is being blocked, though it’s not an error in itself, but rather a symptom of something else :slight_smile: