Arturia's new Pigment plugin crashes with JUCE audio plugin host


#1

The new Pigments plugin from Arturia crashes when you try to open its editor window. This is completely reproducible with the JUCE Audio Plugin Host. How can this be fixed? It’s very odd that the Arturia plugins all run perfectly fine with non-JUCE hosts but break with any JUCE host, as far as we can tell.
Help would be appreciated.

Thread 0 Crashed:: JUCE Message Thread Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x00000001066fc01d objc_msgSend + 29
1 com.Arturia.Pigments.vst3 0x000000012559d544 0x1251b3000 + 4105540
2 com.Arturia.Pigments.vst3 0x0000000125592fb4 0x1251b3000 + 4063156
3 com.Arturia.Pigments.vst3 0x0000000125bd584e 0x1251b3000 + 10627150
4 com.Arturia.Pigments.vst3 0x0000000125bd6cec 0x1251b3000 + 10632428
5 com.apple.CoreFoundation 0x0000000104df03e1 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 17
6 com.apple.CoreFoundation 0x0000000104dd165c __CFRunLoopDoSources0 + 556
7 com.apple.CoreFoundation 0x0000000104dd0b46 __CFRunLoopRun + 934
8 com.apple.CoreFoundation 0x0000000104dd0544 CFRunLoopRunSpecific + 420
9 com.apple.HIToolbox 0x000000010d9b9ebc RunCurrentEventLoopInMode + 240
10 com.apple.HIToolbox 0x000000010d9b9cf1 ReceiveNextEventCommon + 432
11 com.apple.HIToolbox 0x000000010d9b9b26 _BlockUntilNextEventMatchingListInModeWithFilter + 71
12 com.apple.AppKit 0x0000000102e6aa54 _DPSNextEvent + 1120
13 com.apple.AppKit 0x00000001035e67ee -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 2796
14 com.apple.AppKit 0x0000000102e5f3db -[NSApplication run] + 926
15 com.roli.juce.pluginhost 0x0000000100426221 juce::MessageManager::runDispatchLoop() + 161
16 com.roli.juce.pluginhost 0x0000000100426008 juce::JUCEApplicationBase::main() + 1000
17 com.roli.juce.pluginhost 0x0000000100425bbc juce::JUCEApplicationBase::main(int, char const**) + 60
18 com.roli.juce.pluginhost 0x00000001000a0c53 main + 51
19 libdyld.dylib 0x000000010755f235 start + 1


#2

This crash is happening in Arturia’s code, so there’s nothing we can do other than send another email to their tech support to let them know about the issue which I’ll do now.


#3

We’ve also emailed them - but I’m much more concerned as to why their plugins (and Korg Gadgets as well, it now turns out) work perfectly fine with hosts that are not JUCE based. Korg is using JUCE (it’s proudly on your discover page) and I think Arturia is as well. I realize the crashes appear in their codebase but is it possible that something is wrong with the way those plugin editors are being invoked from a JUCE host?


#4

It’s impossible to know without having access to their code and being able to step in and see exactly where the crash occurs. Although given that there are thousands of JUCE based plug-ins out there which don’t crash or show a blank UI when using the JUCE hosting classes, and the JUCE plug-in demos using the latest code don’t either, I’d say the odds are more likely that it’s an error in their code.