Cabbage Logo
Back to Cabbage Site

Ableton 10 Crash (OSX) using generated AU file player example

I figured I should post the info here as well, I had made a new ableton session and was trying out the included cabbage examples that automatically compile to audio unit versions and after playing with one of them for a moment and loading an audio file it produced a somewhat rare ableton crash. I noticed alot of cabbage widget mentions in the stack trace error report so I figured I would post in case this is useful :

Process: Live [13547]
Path: /Applications/Ableton Live 10
Version: 10.0.2 [2018-05-11_f78673c6cd] (10.0.2 [2018-05-11_f78673c6cd])
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Live [13547]
User ID: 501

Date/Time: 2018-07-06 04:00:04.266 -0400
OS Version: Mac OS X 10.13.5 (17F77)
Report Version: 12
Bridge OS Version: 3.0 (14Y664)
Anonymous UUID: F338FF1D-0591-84AB-31AB-B7459C04C189

Sleep/Wake UUID: 5FE4EEA3-2A39-425D-BCCF-7FA0D0D0FCD7

Time Awake Since Boot: 330000 seconds
Time Since Wake: 12000 seconds

System Integrity Protection: enabled

Crashed Thread: 0 MainThread Dispatch queue:

Exception Codes: KERN_INVALID_ADDRESS at 0x0000608001c00000

Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [0]

VM Regions Near 0x608001c00000:
MALLOC_NANO 0000608000000000-0000608001c00000 [ 28.0M] rw-/rwx SM=PRV
MALLOC_NANO 000060c000000000-000060c001800000 [ 24.0M] rw-/rwx SM=PRV

Thread 0 Crashed:: MainThread Dispatch queue:
0 com.cabbageaudio.CabbagePlugin 0x00000001280e0770 CabbageUtilities::getTokens(juce::String, char) + 160
1 com.cabbageaudio.CabbagePlugin 0x00000001280e0279 CabbageWidgetData::getSetofIdentifiersAndParameters(juce::String) + 137
2 com.cabbageaudio.CabbagePlugin 0x00000001280dd137 CabbageWidgetData::setCustomWidgetState(juce::ValueTree, juce::String, juce::String) + 759
3 com.cabbageaudio.CabbagePlugin 0x00000001280d9e2a CabbageWidgetData::setWidgetState(juce::ValueTree, juce::String, int) + 4154
4 com.cabbageaudio.CabbagePlugin 0x0000000128024e07 CabbagePluginProcessor::addImportFiles(juce::StringArray&) + 247
5 com.cabbageaudio.CabbagePlugin 0x00000001280245f7 CabbagePluginProcessor::createCsound(juce::File, bool) + 135
6 com.cabbageaudio.CabbagePlugin 0x00000001280243f9 CabbagePluginProcessor::CabbagePluginProcessor(juce::File, int, int) + 457
7 com.cabbageaudio.CabbagePlugin 0x0000000128023c3c createPluginFilter() + 428
8 com.cabbageaudio.CabbagePlugin 0x000000012816fb24 createPluginFilterOfType(juce::AudioProcessor::WrapperType) + 20
9 com.cabbageaudio.CabbagePlugin 0x00000001280037ef JuceAU::JuceAU(ComponentInstanceRecord*) + 63
10 com.cabbageaudio.CabbagePlugin 0x000000012800fb3e APFactory<AUMIDILookup, JuceAU>::Construct(void*, ComponentInstanceRecord*) + 14
11 com.cabbageaudio.CabbagePlugin 0x0000000128017e2b ComponentBase::AP_Open(void*, ComponentInstanceRecord*) + 75
12 0x00007fff334ce646 APComponent::newInstance(unsigned int, bool, void (ComponentInstanceRecord*, int) block_pointer) + 738
13 0x00007fff33535bef __AudioComponentInstanceNew_block_invoke + 94
14 0x00007fff335a8ea1 Synchronously + 118
15 0x00007fff33535b2b AudioComponentInstanceNew + 209

Thanks I’ll take a look. Do you know if this happens when using the VST version too?

Shoot I can’t seem to find which one it was in the error log text, any idea? Ill try it with vst and see if it happens again, but I forget which one it was… I guess I can try them all again.

The thing that might be causing problems is the fact the AUs are always sandboxed. I’ll need to check but paths too files might be messed up which in turn causes an issue…