vector subscript out of range

[Matt_SF]

Hi folks, I just stumbled upon a little crash which happened on a somewhat big project of mine, while I was testing something with multiple wavetable synth modules.
I saved the project a few minutes before it crashed and now I'm not able to open this particular XML file : it makes HISE crash on start (the previous save is loading correctly though).

Luckily for me I backed up my project before that so, no it's not a big deal but I thought I could share, maybe for debug purposes.
I ran a debug session in VS17 and that's what I got :

je          juce::dsp::DelayLine<float,juce::dsp::DelayLineInterpolationTypes::Linear>::process<juce::dsp::ProcessContextReplacing<float>
int         3  

Exception thrown at 0x00007FFC631C4F69 in HISE Debug.exe: Microsoft C++ exception: hise::HiseJavascriptEngine::RootObject::Error at memory location 0x000000E6400FD188.
JUCE Assertion failure in juce_delayline.h:183

Debug Assertion Failed!

Program: ...andalone\Builds\VisualStudio2017\x64\Debug\App\HISE Debug.exe
File: c:\program files (x86)\microsoft visual studio\2017\community\vc\tools\msvc\14.16.27023\include\vector
Line: 1733

Expression: vector subscript out of range

For information on how your program can cause an assertion
failure, see the Visual C++ documentation on asserts.

As I said it's not done any harm to my project (or so it seems) so I don't really need to debug the issue, I'll try to start over - but maybe it could be useful to someone...
@Christoph-Hart

EDIT : The issue was cause by a script FX that I made before fooling arount with the WT synths. I removed it by editing the XMLPreset file and I'm able now to load the project.

EDIT EDIT : I managed to find what (seem to have) caused the crash. I have a script node FX using some fx.haas nodes. I removed them from the XML file and everything is working fine again.

[ulrik]

@Matt_SF I'm glad you where able to find the issue and that it didn't harm your project

Would you say that working with Script FX is a bit dangerous at the moment, should we be careful and not use it in projects for production?

[Matt_SF]

Thanks mate :thumbs_up:

should we be careful

Scriptnode is usually stable-ish but always save your work frequently and over multiple files (like versioning). Sometimes sample-processing nodes, sometimes simply nesting containers within each other will make HISE crash... But it's a great tool full of possibilities so it would be a shame not to use it - or at least try it. (Try it ! :) )

not use it in projects for production?

It's totally usable in projects for production IMO, but depending on the size/complexity of your project or scriptFx, you might want to take a bit of time checking that everything works as expected.

[d.healey]

@Matt_SF said in vector subscript out of range:

over multiple files (like versioning).

Or use git.

[Matt_SF]

@d-healey said in vector subscript out of range:

Or use git.

Yes that too, I really started to use Git (thanks to you!) but I'm still rather new and I've already managed once or twice to mess things up in my repo. Maybe I became over-careful but now I often use both ways when I'm fooling around with nodes :grinning_face_with_sweat:

[DanH]

@ulrik there’s loads of possibilities and potential but it’s also full of headaches and eats up so much time! However I am using it in projects as I need things that are not available anywhere else and it’s stable (eventually!)