Ableton Crashes

[hisefilo]

Got Ableton live crashes. This part of the report is saying something but no clue what is pointing at. Any idea @Christoph-Hart

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)\
Exception Codes:       KERN_INVALID_ADDRESS at 0xfffffffffffffffc\
Exception Note:        EXC_CORPSE_NOTIFY\
\
Termination Signal:    Segmentation fault: 11\
Termination Reason:    Namespace SIGNAL, Code 0xb\
Terminating Process:   exc handler [26887]\

[Christoph Hart]

I need more context: end user or HISE and which event caused it?

The crash report just says „something is wrong“ ;)

[hisefilo]

@Christoph-Hart got it! Well crash happens on preset changing/loading. Compiled with Hise 2.1.0 IPP enabled. Running on MacOS Mojave 10.14.5. Ableton Live 10. (Also I had this issue in Garageband when changing presets, but I decided to re-save all of the preset because I was thinking .preset xml were corrupt due some new knobs I added on UI after preset creation. Re-saving fixed problem on Garageband. But on Live it persist)

[d.healey]

@hisefilo Have you ran the presets through an XML validator? That can often help find problems.

[Christoph Hart]

What are you doing in your user presets? Are you adding new modules and other dynamic stuff or is it just „simple“ interface value changes?

[hisefilo]

@d-healey will try !!!!

[hisefilo]

@Christoph-Hart simple interface values. Knobs, buttons mainly. But like a lot of them. 200 visible. 200 hidden.

[d.healey]

@hisefilo That's a lot of buttons! Couldn't you replace them with a panel?

[hisefilo]

@d-healey they are placed inside panels. Almost all of them. Just a few on main canvas

[Christoph Hart]

Hmm, you might have to send me a version of your synth (but I can test it next week) - maybe also your project folder so I can make a debug build. Are you using a private repository?

Switching user presets is actually one of the most vurnerable events in HISE since there are multiple threads involved.

[hisefilo]

@Christoph-Hart will do that! :) No rush. Maybe a delay muting engine until everything loads properly. Just a thought

[Christoph Hart]

It already fades out all voices on preset load, then mutes the processing until the preset is loaded.

The problem is that this system involves three threads (UI, loading & audio) operating at the same time and this is extremely hard to get right (also it's a prime example of things that work on some machines, but fail on others)...