VST3 plugin error in DAW

[toxonic]

Since I changed some parameter values in a project's DSP Networks and recompiled them, the compiled VST 3 plugin doesn't run anymore on Linux in Ardour.
Ardour spits out the following cryptic error message after scanning the plugin:

VST3 module-path '/home/toxonic/.vst3/T_Glitch.vst3/Contents/x86_64-linux/T_Glitch.so'
[Info]: Scanning: /home/toxonic/.vst3/T_Glitch.vst3
Error: signal 11
 ---8<---
  /lib/x86_64-linux-gnu/libc.so.6(+0x42520) [0x7fe58b9f0520]
  scriptnode::NodeBase::getNumParameters() const
  /home/toxonic/.vst3/T_Glitch.vst3/Contents/x86_64-linux/T_Glitch.so(+0x9309bf) [0x7fe585f229bf]
  scriptnode::DspNetwork::DspNetwork(hise::ProcessorWithScriptingContent*, juce::ValueTree, bool, snex::ExternalDataHolder*)
  scriptnode::DspNetwork::Holder::restoreNetworks(juce::ValueTree const&)
  hise::JavascriptProcessor::restoreScript(juce::ValueTree const&)
  /home/toxonic/.vst3/T_Glitch.vst3/Contents/x86_64-linux/T_Glitch.so(+0x972636) [0x7fe585f64636]
  hise::Processor::restoreFromValueTree(juce::ValueTree const&)
  hise::Processor::restoreFromValueTree(juce::ValueTree const&)
  hise::ModulatorSynthChain::restoreFromValueTree(juce::ValueTree const&)
  hise::FrontendProcessor::createPreset(juce::ValueTree const&)
  hise::FrontendProcessor::FrontendProcessor(juce::ValueTree&, juce::AudioDeviceManager*, juce::AudioProcessorPlayer*, juce::MemoryInputStream*, juce::MemoryInputStream*, juce::MemoryInputStream*, juce::MemoryInputStream*, juce::ValueTree*, juce::ValueTree*)
  hise::FrontendFactory::createPluginWithAudioFiles(juce::AudioDeviceManager*, juce::AudioProcessorPlayer*)
 --->8---
Scan Failed.

Any ideas on that?

EDIT: Tried some thing, updated to the latest commit, rebuilt the DSP networks as hardcoded fx (cleaned build folder), kicked out the Script FX Module (kept hardcoded master fx)... still the same error after recompiling (clean build folder)!
Then compiled to VST2: Works like a charme! Maybe a VST3 issue?
In earlier commits everything worked fine with VST3...

[Consint]

@toxonic Have you found a solution for this in the meantime? I have just encountered the same problem.