I have been getting frequent crashes with both Redux and Renoise in the past year or two. Usually they just close instantly without any error messages in the GUI or log file, but this one provided an error message and crash backup file.
It occurred as I pressed Ctrl+S to save the project. I took a screenshot to show the state of Renoise when the crash happened. SPAN was the only VST loaded and its GUI was not open.
Operating System: Windows 10 Home 64-bit (10.0, Build 19045) (19041.vb_release.191206-1406)
Processor: Intel(R) Core™ i7-4770 CPU @ 3.40GHz (8 CPUs), ~3.4GHz
Memory: 8192MB RAM
DirectX Version: DirectX 12
User DPI Setting: 96 DPI (100 percent)
DirectX Database Version: 1.0.8
Graphics:
Card name: Intel(R) HD Graphics 4600
Display Memory: 2160 MB
Dedicated Memory: 112 MB
Shared Memory: 2048 MB
Current Mode: 1366 x 768 (32 bit) (60Hz)
PS: A crash that I reported previously has some similarities to this one. They both have a GUI Exception and this crash also involves note-off layers (used in instrument 00):
Thanks for reporting. This seems to happen in combination with one of your installed Renoise Tools - still is a Renoise bug though as scripts never should be able to crash down Renoise.
To ease replicating this, could you send me a zip of all your locally installed tools via a private message or email?
In my Scripting Terminal and Editor, the TestPad.lua had the exact conents of com.Fornicelli.AssignAllMIDIInputs.xrnx → main.lua.
I disabled all of my tools and the crash still occurred when I saved a song (no error message; Renoise just closed abruptly as the song was saving). So I opened the same project and tried saving again and Renoise crashed again.
With all my tools disabled, I wondered if there might be some stuff in TestPad.lua causing it. So I deleted the contents of TestPad.lua and then the project saved successfully with no crashes.
Maybe just a coincidence but probably worth mentioning, since TestPad.lua wasn’t included the Tools folder that I sent.
I do get frequent crashes in Renoise, though unlike this specific case, there usually aren’t any error messages or any indication of a crash in the log file; Renoise will just close immediately without warning.
The crashes seem similar to the behavior of my Redux crashes, where I haven’t noticed any specific action that causes them. They have occurred when saving songs, loading songs, editing samples… though I do have auto backups set to be saved every 5 minutes, so it could be occurring as a result of the autobackups being saved…
I’ve enabled auto backup saving and manually saving my songs frequently, so I haven’t lost much work because of it… I’ve adapted, haha
That’s a simple tool I made to assign the MIDI Input settings of Instruments 00-0F to MIDI channels 1-16 of a chosen device. I’ll attach it the .XRNX this post. I don’t intend on developing it any further or releasing it… twas just a quick tool I wrote for personal use. com.Fornicelli.AssignAllMIDIInputs.xrnx (1.2 KB)
Not saying your crashes have the same origins, but it could be hardware issue related. A while back I had a lot of issues with renoise and my computer and it turned out one of my computer fans didn’t work causing the computer to heat up, crashing whenever a cpu taxing renoise song was playing back. Perhaps think outside of the box?
Yes, I think a hardware problem is possible, since the crashes started happening around the time that I bought a new computer a couple of years ago. Before that Renoise was stable for the ~6-7 years that I had been using it. Though I don’t notice any crashes/unexpected behavior in any other software.
I have a theory that it could be related to a tool that I was using (LiveDive) that hasn’t been updated in years. I would have to constantly disable and re-enable it in the tool browser for it to work properly and maybe it somehow corrupted my Renoise installation? Idk, just an idea since taktik said it seemed to be related to a tool.
Yesterday I uninstalled and reinstalled Renoise (also deleting all Renoise-related folders in appdata/roaming) and I didn’t migrate any of my previous settings, so essentially like a clean “factory reset” I think. For now, the only tool I have installed is SamRender, since that is all I need for the stuff that I’m currently working on. So maybe this new installation might fix the issue. I was able to work for an hour or two yesterday with no problems. =)
No, the song I posted didn’t crash consistently. I was able to load the song from the crash backup and continue working on it without it crashing. Sometimes I’ll remember the everything I did to a song before the crash happens. So I’ll open the song again, repeat the same actions, and Renoise wont crash. So I haven’t found a reliable way to reproduce the problem.
So I got another crash with my new installation today (not the GUI exception; the more frequent case where Renoise simply closes without an error message). It occurred while attempting to save a song. I typed in the name of the xrns in the file browser save dialog and hit the save button, then my entire screen got blurry for a second and Renoise closed.
Here are the Error details from the Windows Event Viewer:
I have quite a few error events from Renoise in my logs and all of the Error events for Renoise have the same exception codes and fault offsets as those 2 events.
The exception codes are the same for my Redux crashes, posted in this thread:
i see. i’m wondering if you wouldn’t mind some suggestions for improvements - because it seems this does not allow for assigning other midi inputs from 10 onwards to 1F for instance, since it’s hardwired to do 00-0F
and if there’s only 3 instruments, then it only sets instrument01-03 instead of creating the 00-0F slots that are missing to cover all midichannels for selected midi device
and also instrument.name is not (nondestructively) modified to show which channel is assigned etc.
