Reproducible crash following track deletions (SOLVED)

Hi, I am a brand new reaper user, still running in eval mode at the moment. I have been getting to know reaper for three days now and have been reasonably successful. Except it is crashing fairly often and I have lost work. At first it seemed intermitant and not as a result of any one action, but following some experimentation I can now reproduce it at will. It has ocurred, at the very least, following pressing the Play button, but the minimum sequence of 100% reproducible events is: 1. Run Reaper (no other apps running) 2. It loads and then auto-loads the last project 3. Select the third track in the list- press the delete key, track is deleted after confirmation dialog 4. Select the next track in the list- press the delete key, track is deleted after confirmation dialog 5. Select the next track in the list- press the delete key, press Ok on the confirmation dialog 6. Reaper immediately crashes. Although I have now reproduced it many times, I only captured the details twice as follows: Problem signature: Problem Event Name: APPCRASH Application Name: reaper.exe Application Version: 3.1.2.0 Application Timestamp: 4ac82bdf Fault Module Name: AF_CHORUS.SEP Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000005 Exception Offset: 000049e6 OS Version: 6.0.6001.2.1.0.768.3 Locale ID: 2057 Additional Information 1: fd00 Additional Information 2: ea6f5fe8924aaa756324d57f87834160 Additional Information 3: fd00 Additional Information 4: ea6f5fe8924aaa756324d57f87834160 Problem signature: Problem Event Name: APPCRASH Application Name: reaper.exe Application Version: 3.1.2.0 Application Timestamp: 4ac82bdf Fault Module Name: AF_CHORUS.SEP Fault Module Version: 0.0.0.0 Fault Module Timestamp: 00000000 Exception Code: c0000005 Exception Offset: 000047d3 OS Version: 6.0.6001.2.1.0.768.3 Locale ID: 2057 Additional Information 1: c71c Additional Information 2: 2ce9896a8b3113ccc8854aafc3a4bbec Additional Information 3: 2dbf Additional Information 4: 966fe2e55afc64d5adb1de36802394b8 I have tried deleting the same three tracks, but in reverse order to above, then it crashed after the second deletion. I did not re-attempt. Following the crash it is possible to restart reaper and everything seems to work ok, except no sound is heard. I have to log out of my Windows session and log back in to restore sound. I am running Vista Home Premium SP1 (32 bit) ASIO4ALL V2.9 PC is a quad core Intel @ 2.4GHz with 2Gb RAM I am liking Reaper immensely, but it is now crashing too often to be of practical use. I hope you will be able to help. I am happy to send the project file in if you need it? Postscript: After posting this in the wrong section (Issue Tracker) I closed Reaper as it had been open on my desktop to get various bits of info out for the bug report. The same crash ocurred as soon as I pressed the X (top right) button to close the window. No track deletions had ocurred, in fact the only thing I had done was open the advanced ASIO driver details within Reaper to get the ASIO version to report. Note also that I suspected ASIO might be the culprit before and set the Audio device to Wave Out. This had no effect on the crash either within that session nor when I restarted everything from a cold start and tried again (after making sure Wave Out was still the output device).

Hi Marv and welcome to the Reaper-forums! There seems to be some chorus plugin in your project, that seems to be the culprit. Take the chorus out or switch it "Offline" (not "Bypass") and try the same procedure again. If you don't hear any sound when you restart Reaper after a crash, the audio driver is still occupied and wasn't released when the crash occured so you have to unload and restart it. If this is not possible you have to restart the system. -Data

Hi, Thanks. I did not specifically add any effects plugins into the project, though I believe one or more of the VSTs I am using has a chorus effect "onboard". I will experiment with this and see what I can do. Note though, that the crash occurs without actually running the project in any way, just deleting the tracks... Update, I have set all FX sends with the VSTs to Off, as some were using a built in chorus effect. However it has had no effect. The crash still ocurrs, though my fave route to reproduce it is just to hit the close [X] button! Further update! It just ocurred immediately after pressing Play, which I did immediately after loading the project. No other edits or activity of any sort.

Hi Marv, thanks for the report. It shows that there is something in your project (not part of Reaper) called AF-CHORUS.ESP that is where the crash is occurring. You can try an internet search to see what that is, and you can maybe get more help if you attach the problem project here. Once you identify what that is, there are some Reaper configuration settings that may help prevent the crash. But bottom line, it's not Reaper that is crashing.

Might have solved it... 

It seems to involve multiple instances of the VST "DSK Synthopia 2" If only one instance is running it behaves fine. If I add a second instance then it always crashes on exit. I took my original crashing project, which had five tracks, three of which were the above named VST and I deleted track by track, saving each time in a new project, until it didn't crash any more on exit. This ocurred at the point of three tracks only one of which was this VST. I loaded and exited several times on this project to prove it was working fine, then added another instance of the VST- Hey presto, crash. Removed it again, and it went back to working fine... I will continue with the project tomorrow studiously avoiding multiple instances of this VST and see if it stays stable.

Thanks Schwa. I now think it is down to this VST. I guess it was my lack of familiarity with the Reaper product which meant I was not able to deduce this myself before raising the bug report. Sorry about that.

Now that you know the culprit you should try this: Open the "add FX" window and find that Synthopia-rascal. Rightclick on it's name and try "buggy plugin compatibility mode" as well as the various options under "run as". You can at least get to the point where a crash of the plug doesn't crash Reaper anymore. You did a good job with this report, crashlogs'n all, Mary. No need to apologize :)