Hi
On Saturday, GP crashed on me for the first time during a gig. It was a difficult few seconds / minutes, but the band carried on. I’m keen to know what might have caused it so am posting my crash report here. It looks like Kontakt 7 but I’m no expert…
Thanks
GigPerformer4-2024-09-14-221113.ips.zip (59.4 KB)
I’ve had 4 in so many days similar to the above.
Plus one that looks different, yesterday (see below):
GigPerformer4-2024-09-16-202400.ips.zip (32.1 KB)
Kontakt was crashing
In the 2nd the Hammond Plugin was crashing
So everything worked fine before these 4 days? What changed?
I see you’re running an older version of GP (4.8.2) — what version of Kontakt 7 are you running? There have been several buggy versions of K7 as well.
Thread 3 Crashed:: com.apple.audio.IOThread.client
0 Kontakt 7 0x422238514 NI::AB::ConstAudioBlock::freeOwnedBuffers() + 36
1 Kontakt 7 0x4207ae320 NI::AB::InterfaceVST3Headless::attachBuffersToHost(Steinberg::Vst::ProcessData&) + 672
2 Kontakt 7 0x4207b0434 NI::AB::InterfaceVST3Headless::process(Steinberg::Vst::ProcessData&) + 1060
3 GigPerformer4 0x1028e95ac 0x1021fc000 + 7263660
4 GigPerformer4 0x1028be9d0 0x1021fc000 + 7088592
5 GigPerformer4 0x1028b990c 0x1021fc000 + 7067916
6 GigPerformer4 0x10290fc18 0x1021fc000 + 7420952
7 GigPerformer4 0x1028458c4 0x1021fc000 + 6592708
8 GigPerformer4 0x102841c44 0x1021fc000 + 6577220
9 CoreAudio 0x1939046e8 HALC_ProxyIOContext::IOWorkLoop() + 9508
10 CoreAudio 0x193901a8c invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 108
11 CoreAudio 0x193a87850 HALC_IOThread::Entry(void*) + 88
12 libsystem_pthread.dylib 0x191091f94 _pthread_start + 136
13 libsystem_pthread.dylib 0x19108cd34 thread_start + 8
The hammond organ crash looks like it is not properly handling a reset call that happens as part of predictive loading.
Thread 0 Crashed:: HotFudge Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x188e795f0 __pthread_kill + 8
1 libsystem_pthread.dylib 0x188eb1c20 pthread_kill + 288
2 libsystem_c.dylib 0x188dbea30 abort + 180
3 libsystem_malloc.dylib 0x188ccedc4 malloc_vreport + 896
4 libsystem_malloc.dylib 0x188cf2ea8 malloc_zone_error + 104
5 libsystem_malloc.dylib 0x188cda7e0 free_list_checksum_botch + 40
6 libsystem_malloc.dylib 0x188cc7fd8 small_free_list_remove_ptr_no_clear + 960
7 libsystem_malloc.dylib 0x188cc3588 small_malloc_from_free_list + 528
8 libsystem_malloc.dylib 0x188cc2cf4 small_malloc_should_clear + 200
9 libsystem_malloc.dylib 0x188cc2b20 szone_malloc_should_clear + 128
10 libc++abi.dylib 0x188e6abd4 operator new(unsigned long) + 32
11 Hammond B-3X 0x3ce102ad8 0x3ce018000 + 961240
12 Hammond B-3X 0x3ce138690 0x3ce018000 + 1181328
13 Hammond B-3X 0x3ce2e333c 0x3ce018000 + 2929468
14 Hammond B-3X 0x3ce2e01f0 0x3ce018000 + 2916848
15 Hammond B-3X 0x3ce0d1b30 0x3ce018000 + 760624
16 GigPerformer4 0x1030754f0 0x102990000 + 7230704
17 GigPerformer4 0x102e7c87c 0x102990000 + 5163132
18 GigPerformer4 0x102e7d8b8 0x102990000 + 5167288
19 GigPerformer4 0x1030f6234 0x102990000 + 7758388
20 GigPerformer4 0x1030f33ac 0x102990000 + 7746476
21 GigPerformer4 0x1030f3250 0x102990000 + 7746128
22 CoreFoundation 0x188f914d8 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28
23 CoreFoundation 0x188f9146c __CFRunLoopDoSource0 + 176
24 CoreFoundation 0x188f911dc __CFRunLoopDoSources0 + 244
25 CoreFoundation 0x188f8fdc8 __CFRunLoopRun + 828
26 CoreFoundation 0x188f8f434 CFRunLoopRunSpecific + 608
27 HIToolbox 0x19373919c RunCurrentEventLoopInMode + 292
28 HIToolbox 0x193738fd8 ReceiveNextEventCommon + 648
29 HIToolbox 0x193738d30 _BlockUntilNextEventMatchingListInModeWithFilter + 76
30 AppKit 0x18c7eecc8 _DPSNextEvent + 660
31 AppKit 0x18cfe54d0 -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700
32 AppKit 0x18c7e1ffc -[NSApplication run] + 476
33 GigPerformer4 0x102f74578 0x102990000 + 6178168
34 dyld 0x188b27154 start + 2476
Predominantly the change from Kontakt 6 to 7
7.10.6, which I believe is the latest
What is the reset call for? Is there perhaps a tweak I can make e.g. delayed loading to help?
Yeah - I just use K6 — I have experienced/seen too many issues with K7 to switch to it.
No, you can’t — this is a part of the plugin SDK and you’re supposed to be able to call it any time. Some plugins simply don’t properly implement this (too many developers make assumptions about how their plugins will be used and don’t properly implement stuff).
In predictive loading, an improperly implemented plugin can cause issues.
1 Like