Crash in 3.4,1 on playback with a specific old song (due to broken automation curves?)

I’m getting intermittent but recurring hard crashes. They occur at the same spot in the song each time.

OS Name: Microsoft Windows 10 Home
OS Version: 10.0.19044 N/A Build 19044
Processor(s): 1 Processor(s) Installed.
[01]: Intel64 Family 6 Model 158 Stepping 9 GenuineIntel ~4200 Mhz
Total Physical Memory: 32,705 MB
Available Physical Memory: 24,944 MB
Virtual Memory: Max Size: 65,473 MB
Virtual Memory: Available: 55,282 MB
Virtual Memory: In Use: 10,191 MB

First it was doing this:

CrashLog: Handling Exception! Code : C0000005
CrashLog: Handling Exception! Code : C0000005
CrashLog: 000000014060EADD: l9_ippsLn_32f_A21 +240FED
CrashLog: 000000014060EADD: l9_ippsLn_32f_A21 +240FED
CrashLog: 0000000140CB1322: l9_ippsLn_32f_A21 +8E3832
CrashLog: 0000000140CB15DD: +8E3AED
CrashLog: 0000000140ABE276: l9_ippsLn_32f_A21 +6F0786
CrashLog: 0000000140D7F70B: l9_ippsLn_32f_A21 +9B1C1B
CrashLog: 0000000140B0E3BE: l9_ippsLn_32f_A21 +7408CE
CrashLog: 00000001407A8C66: l9_ippsLn_32f_A21 +3DB176
CrashLog: 0000000140AD71A9: l9_ippsLn_32f_A21 +7096B9
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 0000000140B1A7AA: l9_ippsLn_32f_A21 +74CCBA
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 0000000140B1A932: l9_ippsLn_32f_A21 +74CE42
CrashLog: 00000001407A8CCC: l9_ippsLn_32f_A21 +3DB1DC
CrashLog: 0000000140AD8C6E: l9_ippsLn_32f_A21 +70B17E
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001406BFFA2: l9_ippsLn_32f_A21 +2F24B2
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00007FFAAF727034: BaseThreadInitThunk +00014
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: FFFFFFFFFFFFFFFF: ??? +00000
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001407A8C91: l9_ippsLn_32f_A21 +3DB1A1
CrashLog: 00000001407CBC71: l9_ippsLn_32f_A21 +3FE181
CrashLog: 00000001407ABCA4: l9_ippsLn_32f_A21 +3DE1B4
CrashLog: 000000014070A769: l9_ippsLn_32f_A21 +33CC79
CrashLog: 000000014071EAA9: l9_ippsLn_32f_A21 +350FB9
CrashLog: 0000000140761F68: l9_ippsLn_32f_A21 +394478
CrashLog: 0000000140719646: l9_ippsLn_32f_A21 +34BB56
CrashLog: 000000014071E8B6: l9_ippsLn_32f_A21 +350DC6
CrashLog: 00000001403FD733: l9_ippsLn_32f_A21 +2FC43
CrashLog: 00000001403F8840: l9_ippsLn_32f_A21 +2AD50
CrashLog: 00000001403FE006: l9_ippsLn_32f_A21 +30516
CrashLog: 0000000140DE6363: l9_ippsLn_32f_A21 +A18873
CrashLog: 00007FFAAF727034: BaseThreadInitThunk +00014

Application: Caught an unhandled fatal exception (Thread: GUI)!
Application: Saving a backup…

Error Message: A fatal error or crash occurred (unhandled exception in thread: GUI).
Error Message: A backup of the current document was saved at
Error Message: ‘C:\Users<USERNAME>\AppData\Roaming\Renoise\V3.4.1\CrashBackups\spirit2_4_1_2022__13_20_crash.xrns’…
Error Message: This either happened because of a bug in Renoise, or because of a bug in one of its loaded components (plugins). Please contact bug@renoise.com and report this problem, so that it can be fixed.
Error Message: Note: It’s very important that we know exactly what has happened (what you were doing before this message popped up), or the problem cannot be replicated/analyzed. Please include a description of what you were doing and which components were being used…

I was using Valhalla Supermassive and Spitfire Audio Labs plugins- and wondered if they were causing the problem so I disabled them. Then I started getting a different hard crash!

CrashLog: Handling Exception! Code : C0000005
CrashLog: 000000014060EADD: l9_ippsLn_32f_A21 +240FED
CrashLog: 0000000140CB1322: l9_ippsLn_32f_A21 +8E3832
CrashLog: 0000000140ABE276: l9_ippsLn_32f_A21 +6F0786
CrashLog: 0000000140B0E3BE: l9_ippsLn_32f_A21 +7408CE
CrashLog: 0000000140AD71A9: l9_ippsLn_32f_A21 +7096B9
CrashLog: 0000000140B1A7AA: l9_ippsLn_32f_A21 +74CCBA
CrashLog: 0000000140B1A932: l9_ippsLn_32f_A21 +74CE42
CrashLog: 0000000140AD8C6E: l9_ippsLn_32f_A21 +70B17E
CrashLog: 00000001406BFFA2: l9_ippsLn_32f_A21 +2F24B2
CrashLog: 00007FFAAF727034: BaseThreadInitThunk +00014
CrashLog: FFFFFFFFFFFFFFFF: ??? +00000

Application: Caught an unhandled fatal exception (Thread: AUDIO SLAVES)!

This happens if I use Directsound and a USB DAC, and also if I use ASIO and my RME Fireface UCX.

Essentially, I’ve had this happen a few times now- it’s as if after a certain point in the song, it’s corrupt, and any attempt to play beyond there causes a crash. If I carefully recover/load without playing, and delete those patterns in the song editor panel on the left, all is well. Then later on, I’ll get to a point that corrupts again, and will have to rinse and repeat. The only difference is that if I am using plugins, GUI seems to throw an exception before audio slaves.

I did once see something go visually askew- the automation lines (for the cutoff of renoise’s own filter effect) jumped apparently out of bounds, giving a solid-looking editing region. No chance of a screenshot, as it bombed out quickly and I can’t repro on demand. However, it looks like something is broken in the automation editing, if I had to guess, and it makes other parts of renoise break due to corrupt values? This is could be very wide of the mark, of course- but it’s annoyingly intermittent, so hard to be more specific.

If I find any repro or other faintly useful details, I will try try to update this. It’s irritatingly vague :slight_smile:

Can you share the song file?

1 Like

Yes, will be hard to track this down without seeing the song.
If you don’t want to share the song file with everyone here you can also send me a private forum message or send it via email to us. That would be very helpful.

First of all, whichever helpful soul changed the title, please don’t. It wasn’t an old song. It was started in the current demo, and then continued (from basically a few barebones patterns) in 3.4.1. The thread title was chosen for a reason.

Hey @taktik - can send you an example version of the song which will always cause a hard crash around pattern 19. I fully expect you’ll find some weird mangled automation values or something- as occasionally, when drawing automation envelopes, nodes seemed to jump out of bounds. If it helps you nail down a bug, happy to help.

Edit: I might be a dumbass, but I can’t see how to PM on this forum- is it enabled for my account? In any case, I will drop an email to bugs@ and support@ with a suitably crashy song fragment attached.

For myself, I managed to chop the end off the song, and continue with it (for good or ill :smiley: ).

Hi there!

Could you possibly direct message me this track? I’m interested in finding out what the bug for this may have been? Did you ever find out?

Many thanks in advance!