Crashes while rendering in Ableton Live, related to render oversampling

[mustgroove]

For a while now, I've had my oversampling set to 2x for realtime and 16x for rendering in my Settings.xml file. But recently I've started getting a lot of crashes while rendering certain projects which seems to be caused by Sylenth:

a) A lot of the time, Live crashes with a "Live has caused a serious error" message, in which case macOS doesn't generate a crashlog. But sometimes it does crash the "usual" way where a macOS crash log is generated, and the crashed thread will Sylenth is always mentioned.

b) The crashing stops if I freeze tracks that contain Sylenth first. After that, rendering the whole project doesn't crash anymore.

I'm keen to keep the render quality as high as possible, but hoping these crashes can be solved. Any further details I can provide to help get to the bottom of this?


Edit - should also mention this is on Mojave 10.14.6, running Sylenth 3.067. Also I tried changing render oversampling back to 1 in Settings.xml and that also fixes the crashes, so these crashes definitely seem to be related to the render oversampling setting.

[mustgroove]

Crash report excerpts:

Crashed Thread: 252 AudioCalc

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000080
Exception Note: EXC_CORPSE_NOTIFY

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

Thread 252 Crashed:: AudioCalc
0 com.LennarDigital.Sylenth1 0x000000023f64e635 main_macho + 337269
1 com.LennarDigital.Sylenth1 0x000000023f64e02c main_macho + 335724
2 com.LennarDigital.Sylenth1 0x000000023f64d6c1 main_macho + 333313
3 com.LennarDigital.Sylenth1 0x000000023f64cb61 main_macho + 330401
4 com.LennarDigital.Sylenth1 0x000000023f634a25 main_macho + 231781
5 com.LennarDigital.Sylenth1 0x000000023f61a966 main_macho + 125094
6 com.LennarDigital.Sylenth1 0x000000023f62f9d0 main_macho + 211216
7 com.LennarDigital.Sylenth1 0x000000023f6c755a main_macho + 832666
8 com.LennarDigital.Sylenth1 0x000000023f6c7b28 main_macho + 834152
9 com.LennarDigital.Sylenth1 0x000000023f60092e main_macho + 18542
10 com.ableton.live 0x00000001120762ee 0x10fc1d000 + 38114030
11 com.ableton.live 0x0000000112075fa7 0x10fc1d000 + 38113191
12 com.ableton.live 0x000000011205d93e 0x10fc1d000 + 38013246
13 com.ableton.live 0x0000000110f6a1c5 0x10fc1d000 + 20238789
14 com.ableton.live 0x0000000110f8a64d 0x10fc1d000 + 20371021
15 com.ableton.live 0x0000000110f6dc2a 0x10fc1d000 + 20253738
16 com.ableton.live 0x0000000110f6df6e 0x10fc1d000 + 20254574
17 com.ableton.live 0x00000001109d58eb 0x10fc1d000 + 14387435
18 com.ableton.live 0x00000001109d5abe 0x10fc1d000 + 14387902
19 libsystem_pthread.dylib 0x00007fff6a7ea2eb _pthread_body + 126
20 libsystem_pthread.dylib 0x00007fff6a7ed249 _pthread_start + 66
21 libsystem_pthread.dylib 0x00007fff6a7e940d thread_start + 13

[4damind]

Interesting... apparently still relevant in 2022. I had many crashes in Cubase with several instances of Sylenth and 16x oversampling when exporting. The crash dump always said "Heap corruption".
Lennard Digital recommended to delete the settings and reinstall Sylenth (which then also resets oversampling to 1).

The question would be: what is the recommended max "safe" value for oversampling and is this problem under observation for a possible fix?

[mustgroove]

On both my previous (Intel) and current (M1) Macbook Pro, render oversampling has been crash-free at 8x - give it a try and see how you go.