Crash! 💥 Please Help!

Jedikeyz66 · April 12, 2026, 3:18pm

Posted this in FB, was told to bring it up here! Thanks for adding me! So…….

First gig with my Gig Performer 5, 2 keyboard controller set up. It was the most embarrassing gig I’ve had in almost 20 years.

I’m using:

MacBook Air M3, 16G Ram, 2TB SSD

2 Arturia Controllers. Keylab & an Essential

VST3’s/Plug-ins:

Kontakt 7, Kontakt 8, Keyscape, Reason 13(effects racks), Arturia Analog Lab Pro, Roland D-50, Korg Trinity, Korg Triton, Korg Triton Extreme, Korg M1, Korg Wavestation(All up to date)

I made about 6 racks, 4 that I actually used for the show. Each has instances of Kontakt, various Korg’s, Keyscape on 2 of them, Reason 13 effect racks, not too much midi other than some sliders for volume. :::::

I just purchased Gig Performer a few weeks back. Spent roughly 30-40 hours or more meticulously setting up these racks. I performed at this festival with hundreds in attendance. In the middle of the show, right before a lead/melody, Gig Performer literally just vanished. Yes it crashed. Didn’t come back up on its own. Just went away in the blink of an eye. I tried loading it back up once and it didn’t respond. Tried again and it worked, the band gave me sneers. So embarrassing.

Any ideas what I should do? During the weeks of creating my racks, I had trouble here and there but not like this. I purchased this to replace Mainstage, and not even Mainstage did this to me. Do they give refunds? or any help would be wonderful.

aharry · April 12, 2026, 3:23pm

Gig Performer is a plugin host and is extremely stable. What’s not always stable are the myriad of plugins that can be hosted in Gig Performer, which is certainly the cause of your crashing.

I would seek out any crash reports you can find and submit them for review by the developers. There are several threads here that can guide you on locating the reports.

Charles · April 12, 2026, 3:27pm

When it crashed, do you know what Rackspace you were in and what plugins were active?

Have you had time to try to reproduce the issue?

(I am in the middle of troubleshooting an issue with Blue3 and understand this can be frustrating!)

pianopaul · April 12, 2026, 3:31pm

Can you upload a crashlog?
You should find it with the console application.

dhj · April 12, 2026, 3:54pm

He is on a Mac. Instructions for getting Windows crash reports won’t help (but thanks for takin the time to respond)

Jedikeyz66 · April 12, 2026, 3:55pm

Yes I’m running the latest Mac OS Tahoe

Jedikeyz66 · April 12, 2026, 3:56pm

Yes I do, the top keyboard had Kontakt 7 & Korg Triton, bottom keyboard had Kontakt 8, Korg M1 & Keyscape

Charles · April 12, 2026, 3:56pm

woops

dhj · April 12, 2026, 4:03pm

Ok, obviously I have not seen the crash report yet (you need to open the Console app and look for crash report there) but I can already point at several possibilities

Mixing different versions of Kontakt is an absolute no-no. This is a well known problem (with Kontakt, not with GP ) though it took us about a month to figure it out, along with help from Native Instruments. We have a blog article somewhere describing the steps we took that ultimately led to the problem.
Some of those Korg plugins are also known to be buggy. Korg has acknowledged the issues (we love Korg) but I don’t know when fixes will be available.
Is that Roland D50 part of the Roland Cloud? Roland has a horrible licensing process that seems to require access to their remote services for license confirmation and if that fails, some of those plugins just crash, bringing everything down with them.

I’m not pointing specifically at any of these (though I know for certain that 1 above is definitely a problem) so let’s see the crash report asap.

dhj · April 12, 2026, 4:06pm

That has its own issues. While we know that GP itself runs ok on Tahoe it’s not clear that all plugins have been validated for it. Tahoe has a lot of bugs.

From a simple search:
Upgrading to macOS 26 Tahoe can cause VST plugin instability, with some users reporting plugin crashes in DAWs like Logic Pro 12, while others experience no issues. Key issues include incompatibility with older plugins, Waves plugin failures, and graphical glitches. Many developers currently recommend waiting to upgrade until they confirm full compatibility

Jedikeyz66 · April 12, 2026, 4:37pm

Thank you and everyone else for the solid info. When I get home(still on the road) I will find the report and post it here. It seems like there are a lot of bugs to work out between the variety of developers and their universal compatibility and reliability with GP. For the time being I will be having to use my Korg Nautilus and another board. I was super hyped about GP because my set up (racks)I described is exactly how I have it set up in Mainstage. I just worry that Mainstage will crash on me. It hasn’t yet but years ago it did at a huge gig and it was the worst. Ultimately MacBook and controllers are way lighter to lug around, that’s why I was wanting to use it again

npudar · April 12, 2026, 5:05pm

Until you post the crash logs, you can review the following articles:

dhj · April 12, 2026, 5:16pm

The issues aren’t typically tied to GP (unless there is actually a GP bug) but rather that plugin developers sometimes make assumptions that are not necessarily valid.

If the issue is ours, we will most certainly fix it as a high priority but it is most likely that something else happened so we are really keen to see that crash report as soon as you can get it to us,

Jedikeyz66 · April 12, 2026, 6:46pm

I can only wonder. I use all of these VST3’s/plug ins with Mainstage, Reason 13 and especially Ableton Live12 and have never had an issue with any of them. The plug ins or the DAW’s. I get that GP is solid build, I am just curious as to why they are failing in GP but not in the others.

npudar · April 12, 2026, 7:04pm

Keep testing and try to crash first with an Intrernet connection and afterward offline.

And make sure to post the crash logs here.

They will show the culprit.

Almost all cases are related to plugins.
Once reported, plugin devs usually fix them in a reasonable time.

I compile some of the reports here: [blog] How to find out which plugin crashed Gig Performer - #20 by npudar

dhj · April 12, 2026, 7:17pm

No, you don’t. Mainstage does not support VST or VST3 formats, you must use the AU format. And because Apple applications are the only one that REQUIRE the AU format, many developers don’t test the AU format with other plugin hosts.

GP tends to exercise more of the APIs used for implementing plugins than do many other hosts (including DAWs) and sometimes plugin developers don’t implement some of those APIs properly or they make assumptions that they shouldn’t and that’s generally what leads to problems.

For example, some developers assume incorrectly that the Window Handle they are given for a plugin editor window will always be valid so they cache it and reuse it. Some plugin hosts do reuse the handle but you don’t have to (and we don’t) and so depending on that assumption can be an issue.

Another thing we’ve seen from time to time is that some plugins don’t like being “reset”. The developer has made the (invalid) assumption that a plugin will never be reset more than once when it’s first loaded. But in GP, there can be several cases where we do want to reset plugins (predictive loading is a good example) and a plugin that doesn’t tolerate being reset can crash.

There are other cases where we have seen some strange behavior, again due to invalid assumptions about how the plugin will be used. I won’t mention names but we encountered an effects plugin once from a well-known company that did audio processing only, no MIDI and so no MIDI port was exposed. In a channel strip model this is not an issue because MIDI events don’t get passed into an audio effects plugin but the GP paradigm is much more general and if a plugin should not respond to MIDI events it should be ignoring MIDI that arrives along the way but this plugin was processing MIDI events coming from controllers anyway and so parameters got changed unexpectedly.

You’d be surprised at some of the things we’ve seen.

Jedikeyz66 · April 13, 2026, 5:30am

Honestly can’t say I know the difference between AU and VST/VST3 etc. I just know when I use them in Mainstage they don’t crash. When I use them in Ableton Live or Reason 13, they run fine also. We just got home. Tomorrow I will dig into my MacBook and post the reports. Thank y’all for the assistance

npudar · April 13, 2026, 8:06am

[blog] Which plugin format is better: VST vs VST3 vs AU

There is a blog article for every topic.
You can see that there may be differences between formats in terms of behavior, stability, and functionality.

Jedikeyz66 · April 14, 2026, 9:53pm

Translated Report (Full Report Below)

Process: GigPerformer5 [1293]
Path: /Users/USER/Desktop/GigPerformer5.app/Contents/MacOS/GigPerformer5
Identifier: com.deskew.gigperformer5
Version: 5.1.6 (5.1.6)
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: com.deskew.gigperformer5 [1050]
User ID: 501

Date/Time: 2026-04-11 15:23:45.6093 -0500
Launch Time: 2026-04-11 14:23:24.0877 -0500
Hardware Model: Mac15,12
OS Version: macOS 26.4.1 (25E253)
Release Type: User

Crash Reporter Key: BAB8A30C-8BB4-A58B-0089-23D613A33467
Incident Identifier: 56B7AFA0-4C62-420E-AB92-21F51923C7A7

Time Awake Since Boot: 4300 seconds

System Integrity Protection: enabled

Triggered by Thread: 280 IndexingThread

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Subtype: FS pagein error: 22 Invalid argument
Exception Codes: 0x000000000000000a, 0x0000000112648000

Termination Reason: Namespace SIGNAL, Code 10, Bus error: 10
Terminating Process: exc handler [1293]

VM Region Info: 0x112648000 is in 0x112648000-0x112650000; bytes after start: 0 bytes before end: 32767
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
MALLOC metadata 1125c8000-112648000 [ 512K] rw-/rwx SM=PRV
—> mapped file 112648000-112650000 [ 32K] rw-/rwx SM=ALI Object_id=49ee2c67
MALLOC metadata 112650000-1126d0000 [ 512K] rw-/rwx SM=PRV

Kernel Triage:
CL - (arg = 0x0) cluster_pagein past EOF
APFS - (arg = 0x3be2001600200040) cluster_pagein() failed
VM - (arg = 0x1900000016) Filesystem pagein returned an error in vnode_pagein
VM - (arg = 0x0) Page has error bit set

Thread 0:: HotFudge Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x1809b3c34 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x1809c6574 mach_msg2_internal + 76
2 libsystem_kernel.dylib 0x1809bc9c0 mach_msg_overwrite + 480
3 libsystem_kernel.dylib 0x1809b3fc0 mach_msg + 24
4 CoreFoundation 0x180ab4d68 __CFRunLoopServiceMachPort + 160
5 CoreFoundation 0x180ab3654 __CFRunLoopRun + 1188
6 CoreFoundation 0x180b85be0 _CFRunLoopRunSpecificWithOptions + 532
7 HIToolbox 0x18d888560 RunCurrentEventLoopInMode + 320
8 HIToolbox 0x18d88b8bc ReceiveNextEventCommon + 488
9 HIToolbox 0x18da1513c _BlockUntilNextEventMatchingListInMode + 48
10 AppKit 0x18558b1a4 _DPSBlockUntilNextEventMatchingListInMode + 228
11 AppKit 0x184edf084 _DPSNextEvent + 576
12 AppKit 0x185a7469c -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 688
13 AppKit 0x185a743a8 -[NSApplication(NSEventRouting) nextEventMatchingMask:untilDate:inMode:dequeue:] + 72
14 AppKit 0x184ed213c -[NSApplication run] + 368
15 GigPerformer5 0x10322f688 0x102b60000 + 7141000
16 dyld 0x18063bda4 start + 6992

Thread 1:: com.apple.NSEventThread
0 libsystem_kernel.dylib 0x1809b3c34 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x1809c6574 mach_msg2_internal + 76
2 libsystem_kernel.dylib 0x1809bc9c0 mach_msg_overwrite + 480
3 libsystem_kernel.dylib 0x1809b3fc0 mach_msg + 24
4 CoreFoundation 0x180ab4d68 __CFRunLoopServiceMachPort + 160
5 CoreFoundation 0x180ab3654 __CFRunLoopRun + 1188
6 CoreFoundation 0x180b85be0 _CFRunLoopRunSpecificWithOptions + 532
7 AppKit 0x185000c64 _NSEventThread + 184
8 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
9 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 2:: caulk.messenger.shared:17
0 libsystem_kernel.dylib 0x1809b3bb0 semaphore_wait_trap + 8
1 caulk 0x18d330e00 caulk::semaphore::timed_wait(double) + 224
2 caulk 0x18d330cac caulk::concurrent::details::worker_thread::run() + 32
3 caulk 0x18d33094c void* caulk::thread_proxy<std::__1::tuple<caulk::attributes, void (caulk::concurrent::details::worker_thread::)(), std::__1::tuplecaulk::concurrent::details::worker_thread*>>(void) + 96
4 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
5 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 3:: caulk.messenger.shared:high
0 libsystem_kernel.dylib 0x1809b3bb0 semaphore_wait_trap + 8
1 caulk 0x18d330e00 caulk::semaphore::timed_wait(double) + 224
2 caulk 0x18d330cac caulk::concurrent::details::worker_thread::run() + 32
3 caulk 0x18d33094c void* caulk::thread_proxy<std::__1::tuple<caulk::attributes, void (caulk::concurrent::details::worker_thread::)(), std::__1::tuplecaulk::concurrent::details::worker_thread*>>(void) + 96
4 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
5 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 4:: com.apple.audio.IOThread.client
0 TRITON 0x15054e400 korg::triton::TritonLibrary::OnFsConvProcessReplacingSafe(float**, float**, unsigned int) + 19180
1 ??? 0x7032a9338 ???
2 TRITON 0x1505498d0 korg::triton::TritonLibrary::OnFsConvProcessReplacing(float**, float**, unsigned int) + 92
3 TRITON 0x15015be34 TritonPluginAudioProcessor::processBlock(juce::AudioBuffer&, juce::MidiBuffer&) + 180
4 TRITON 0x150477044 void juce::JuceVST3Component::processAudio(Steinberg::Vst::ProcessData&) + 292
5 TRITON 0x15046f828 juce::JuceVST3Component::process(Steinberg::Vst::ProcessData&) + 528
6 GigPerformer5 0x10333b23c 0x102b60000 + 8237628
7 GigPerformer5 0x103332ad4 0x102b60000 + 8202964
8 GigPerformer5 0x1033106f8 0x102b60000 + 8062712
9 GigPerformer5 0x10330b9a4 0x102b60000 + 8042916
10 GigPerformer5 0x103365430 0x102b60000 + 8410160
11 GigPerformer5 0x103297870 0x102b60000 + 7567472
12 GigPerformer5 0x103293c50 0x102b60000 + 7552080
13 CoreAudio 0x183d44fbc HALC_ProxyIOContext::IOWorkLoop() + 10448
14 CoreAudio 0x183d42050 invocation function for block in HALC_ProxyIOContext::HALC_ProxyIOContext(unsigned int, unsigned int) + 172
15 CoreAudio 0x183f000b0 HALC_IOThread::Entry(void*) + 88
16 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
17 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 5:
0 libsystem_kernel.dylib 0x1809b3c34 mach_msg2_trap + 8
1 libsystem_kernel.dylib 0x1809c6574 mach_msg2_internal + 76
2 libsystem_kernel.dylib 0x1809bc9c0 mach_msg_overwrite + 480
3 libsystem_kernel.dylib 0x1809b3fc0 mach_msg + 24
4 CoreMIDI 0x19ff9a61c XServerMachPort::ReceiveMessage(int&, void*, int&) + 104
5 CoreMIDI 0x19ffbc160 MIDIProcess::MIDIInPortThread::Run() + 148
6 CoreMIDI 0x19ffb0574 CADeprecated::XThread::RunHelper(void*) + 40
7 CoreMIDI 0x19ffbb8fc CADeprecated::CAPThread::Entry(void*) + 96
8 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
9 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 6:: JUCE Timer
0 libsystem_kernel.dylib 0x1809b750c __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1809f8128 _pthread_cond_wait + 980
2 GigPerformer5 0x1033716b0 0x102b60000 + 8459952
3 GigPerformer5 0x1033ba160 0x102b60000 + 8757600
4 GigPerformer5 0x10337cb58 0x102b60000 + 8506200
5 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
6 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 7:: GPScriptRT
0 libsystem_kernel.dylib 0x1809b750c __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1809f8128 _pthread_cond_wait + 980
2 GigPerformer5 0x102c7fc84 0x102b60000 + 1178756
3 GigPerformer5 0x10337cb58 0x102b60000 + 8506200
4 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
5 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 8:: ActionScheduler
0 libsystem_kernel.dylib 0x1809b750c __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1809f8128 _pthread_cond_wait + 980
2 GigPerformer5 0x1033716b0 0x102b60000 + 8459952
3 GigPerformer5 0x102d4c54c 0x102b60000 + 2016588
4 GigPerformer5 0x10337cb58 0x102b60000 + 8506200
5 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
6 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 9:
0 libsystem_kernel.dylib 0x1809b9fc4 kevent + 8
1 GigPerformer5 0x1031fe220 0x102b60000 + 6939168
2 GigPerformer5 0x103204260 0x102b60000 + 6963808
3 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
4 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 10:
0 libsystem_kernel.dylib 0x1809b750c __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1809f8128 _pthread_cond_wait + 980
2 libc++.1.dylib 0x18090d8f0 std::__1::condition_variable::__do_timed_wait(std::__1::unique_lockstd::__1::mutex&, std::__1::chrono::time_point<std::__1::chrono::system_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 1000000000l>>>) + 104
3 GigPerformer5 0x1032140f8 0x102b60000 + 7028984
4 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
5 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 11:
0 libsystem_kernel.dylib 0x1809b9fc4 kevent + 8
1 GigPerformer5 0x1031fe220 0x102b60000 + 6939168
2 GigPerformer5 0x103213834 0x102b60000 + 7026740
3 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
4 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 12:
0 libsystem_kernel.dylib 0x1809b750c __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1809f8128 _pthread_cond_wait + 980
2 libc++.1.dylib 0x18090d858 std::__1::condition_variable::wait(std::__1::unique_lockstd::__1::mutex&) + 32
3 GigPerformer5 0x1030080fc 0x102b60000 + 4882684
4 GigPerformer5 0x10300828c 0x102b60000 + 4883084
5 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
6 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 13:
0 libsystem_kernel.dylib 0x1809b750c __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1809f8128 _pthread_cond_wait + 980
2 libc++.1.dylib 0x18090d858 std::__1::condition_variable::wait(std::__1::unique_lockstd::__1::mutex&) + 32
3 GigPerformer5 0x1030080fc 0x102b60000 + 4882684
4 GigPerformer5 0x10300828c 0x102b60000 + 4883084
5 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
6 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Thread 14:
0 libsystem_kernel.dylib 0x1809b750c __psynch_cvwait + 8
1 libsystem_pthread.dylib 0x1809f8128 _pthread_cond_wait + 980
2 libc++.1.dylib 0x18090d858 std::__1::condition_variable::wait(std::__1::unique_lockstd::__1::mutex&) + 32
3 GigPerformer5 0x1030080fc 0x102b60000 + 4882684
4 GigPerformer5 0x10300828c 0x102b60000 + 4883084
5 libsystem_pthread.dylib 0x1809f7c58 _pthread_start + 136
6 libsystem_pthread.dylib 0x1809f2c1c thread_start + 8

Jedikeyz66 · April 14, 2026, 9:55pm

Thread 280 Crashed:: IndexingThread
0 libsystem_platform.dylib 1 Reason Rack Plugin 2 Reason Rack Plugin 3 Reason Rack Plugin 4 Reason Rack Plugin 5 Reason Rack Plugin 6 Reason Rack Plugin 7 Reason Rack Plugin 8 Reason Rack Plugin 9 Reason Rack Plugin 10 Reason Rack Plugin 11 Reason Rack Plugin 12 Reason Rack Plugin 13 Reason Rack Plugin 14 Reason Rack Plugin 15 Reason Rack Plugin 16 Reason Rack Plugin 17 Reason Rack Plugin 18 Reason Rack Plugin 19 Reason Rack Plugin 20 Reason Rack Plugin 21 libsystem_pthread.dylib 22 libsystem_pthread.dylib 0x180a010b0 __bzero + 32
0x164c9c164 0x163a44000 + 19235172
0x164c9aba0 0x163a44000 + 19229600
0x164c99ef8 0x163a44000 + 19226360
0x164c9e56c 0x163a44000 + 19244396
0x164cc1558 0x163a44000 + 19387736
0x164cc2c80 0x163a44000 + 19393664
0x164cbaeb4 0x163a44000 + 19361460
0x164cbcc84 0x163a44000 + 19369092
0x164cb0574 0x163a44000 + 19318132
0x164c7d5b0 0x163a44000 + 19109296
0x1647c829c 0x163a44000 + 14172828
0x164302c64 0x163a44000 + 9170020
0x164300614 0x163a44000 + 9160212
0x1642fe9e4 0x163a44000 + 9152996
0x16430e9a0 0x163a44000 + 9218464
0x16430c2d8 0x163a44000 + 9208536
0x16430be98 0x163a44000 + 9207448
0x16430a7d0 0x163a44000 + 9201616
0x1643099ac 0x163a44000 + 9197996
0x16451955c 0x163a44000 + 11359580
0x1809f7c58 _pthread_start + 136
0x1809f2c1c thread_start + 8