[6.24]New version causing crashing in large project (FIXED)

o_ciz · 03-04-2021, 12:47 PM

Hello,

I installed the latest version of Reaper (6.24). Everything was working correctly in smaller projects until I tried to load my large orchestral project with lots of tracks and RAM heavy samples.

I was able to play the instruments and do other stuff. However when I clciked Play the button appeared to be pressed but there was no playback and the playhead was not moving. When I tried to click somewhere the Reaper became unresponsive and had to be shut down. This was happening every time I loaded the project (I tried multiple times).

After reading some suggestions on this forum I tried to remove external scripts that I am using and found out that this behaviour had probably something to do with Reaticulate that I use in the project. When I removed all instances of Reaticulate the problem with playback not starting was resolved.

I created new Reaticulate instances from the scratch (because it is essential for my workflow) and the playback was still working so I thought the issue was solved. But after short time my Reaper just crashed during playback. So this only changed the problem from playback not working at all to Reaper crashing at random times during the playback.

I tried again to remove Reaticulate from the project and did not experience any crashes. No errors are happening when reaticulate is loaded and instruments are offline. I tried to roll back to 6.23 and everything is working fine in the previous version.

Here is the crash log from Event Viewer:

Faulting application name: reaper.exe, version: 6.2.4.0, time stamp: 0x603ed880
Faulting module name: reaper.exe, version: 6.2.4.0, time stamp: 0x603ed880
Exception code: 0xc0000005
Fault offset: 0x000000000048c26d
Faulting process id: 0x8
Faulting application start time: 0x01d71124fae45da7
Faulting application path: C:\Program Files\REAPER (x64)\reaper.exe
Faulting module path: C:\Program Files\REAPER (x64)\reaper.exe
Report Id: 26cfcbb2-95ea-43e5-9cd3-89cc618928d8
Faulting package full name:
Faulting package-relative application ID:

My PC specs are:

Windows 10
Focusrite Scarlett Solo 3rd Generation
CPU Intel Core i7-9700
32 GB RAM

The issue is probably caused by Reaticulate but I do not want to stop using it as I am very much used to it. I could always use the older version of Reaper but maybe someone with more experince could propose some solutions?

Thank you

Justin · 03-04-2021, 01:51 PM

That crash address indicates midi_List::EnumItems().

If you can make a dump file, we can determine if it's our fault or Reaticulate, probably.

_Stevie_ · 03-04-2021, 02:08 PM

I have exactly the same issue! I was going mad, I thought it's only me.
I only have this with very specific projects.
In the very moment, I press the play button, Reaper crashes.
But it's totally random.

Let me add my crashlog, too, if it stems from the same error.
BRB!

Code:

Name der fehlerhaften Anwendung: reaper.exe, Version: 75.220.225.57, Zeitstempel: 0x60256457
Name des fehlerhaften Moduls: reaper.exe, Version: 75.220.225.57, Zeitstempel: 0x60256457
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000004973c5
ID des fehlerhaften Prozesses: 0x51ec
Startzeit der fehlerhaften Anwendung: 0x01d71137158eeb5a
Pfad der fehlerhaften Anwendung: C:\Program Files\REAPER (x64)\reaper.exe
Pfad des fehlerhaften Moduls: C:\Program Files\REAPER (x64)\reaper.exe
Berichtskennung: 923197bf-13a8-420e-ae1b-b32654e79e8f
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Code:

Name der fehlerhaften Anwendung: REAPER.exe, Version: 75.220.225.57, Zeitstempel: 0x60256457
Name des fehlerhaften Moduls: REAPER.exe, Version: 75.220.225.57, Zeitstempel: 0x60256457
Ausnahmecode: 0xc0000005
Fehleroffset: 0x00000000004973c5
ID des fehlerhaften Prozesses: 0x51bc
Startzeit der fehlerhaften Anwendung: 0x01d71136ae82fde1
Pfad der fehlerhaften Anwendung: C:\Program Files\REAPER (x64)\REAPER.exe
Pfad des fehlerhaften Moduls: C:\Program Files\REAPER (x64)\REAPER.exe
Berichtskennung: 628be1fb-1f73-4d39-a60f-3feba06cfa3d
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Code:

Name der fehlerhaften Anwendung: reaper.exe, Version: 74.12.171.169, Zeitstempel: 0x602aab64
Name des fehlerhaften Moduls: reaper.exe, Version: 74.12.171.169, Zeitstempel: 0x602aab64
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000049755d
ID des fehlerhaften Prozesses: 0x4a30
Startzeit der fehlerhaften Anwendung: 0x01d7112e901bb169
Pfad der fehlerhaften Anwendung: C:\Program Files\REAPER (x64)\reaper.exe
Pfad des fehlerhaften Moduls: C:\Program Files\REAPER (x64)\reaper.exe
Berichtskennung: adb38a6a-4993-42a6-ae5a-c490996f7791
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

Code:

Name der fehlerhaften Anwendung: REAPER.exe, Version: 74.12.171.169, Zeitstempel: 0x602aab64
Name des fehlerhaften Moduls: REAPER.exe, Version: 74.12.171.169, Zeitstempel: 0x602aab64
Ausnahmecode: 0xc0000005
Fehleroffset: 0x000000000049755d
ID des fehlerhaften Prozesses: 0x5324
Startzeit der fehlerhaften Anwendung: 0x01d7112e35be8fc6
Pfad der fehlerhaften Anwendung: C:\Program Files\REAPER (x64)\REAPER.exe
Pfad des fehlerhaften Moduls: C:\Program Files\REAPER (x64)\REAPER.exe
Berichtskennung: 5184e00f-b3f0-4bec-8ddc-8b6ccaf14c52
Vollständiger Name des fehlerhaften Pakets: 
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:

And yes, I had quite a bunch of crashes today...

_Stevie_ · 03-04-2021, 02:38 PM

I'm also using Reaticulate btw...

I switched back to 6.21 dev202a (random pick, because anything 6.23 dev did have the same issue) and so far the problem seems gone.

Justin · 03-04-2021, 02:49 PM

Quote:

Originally Posted by _Stevie_

And yes, I had quite a bunch of crashes today...

Those you posted are 6.23+dev0211 and 0215, but the crash is similar to the OP. Can I get a dump file please? Thanks!

_Stevie_ · 03-04-2021, 02:53 PM

Yeah, because the issue literally manifested itself in several builds.
I'm on crash dump hunt...

Justin · 03-04-2021, 02:57 PM

(edit) If it just quits to desktop, there's a registry key you need to set to have it create a dump file, let me find that. Ah yes, here: https://helpx.adobe.com/xd/kb/how-to...s-machine.html

_Stevie_ · 03-04-2021, 03:18 PM

Funnily, it has created crash dumps of the whole day.
There are also dev304 dumps. I will just zip them all and post them here.

EDIT: will send the link via mail.

o_ciz · 03-04-2021, 03:42 PM

Quote:

Originally Posted by _Stevie_

Yeah, because the issue literally manifested itself in several builds.
I'm on crash dump hunt...

That´s interesting. I have never experienced this error in any previous builds.

I have some trouble creating the dump file because the project is taking up almost all of my 32GB of RAM and the dump file is therefore huge and I don´t have enough space on my drive :-D. But I will try to do it somehow.

_Stevie_ · 03-04-2021, 04:26 PM

It doesn't happen with all of my projects. Maybe out of 80, 2 were affected.

@Justin: Do you need more dumps?

Justin · 03-04-2021, 05:41 PM

Got it, thanks! Looks like it is the JS: Reaticulate causing the crash, but the crash is almost certainly our fault... can you send a few .rpp files our way too?

_Stevie_ · 03-04-2021, 05:43 PM

Amazing, thanks for checking into!

Yes, I can ZIP all the projects that gave me headaches the last few days

(thankfully I took notes). Sending them your way via mail in the next minutes.

Justin · 03-04-2021, 06:12 PM

Got them, thanks! Anything in particular to trigger the crash?

Are you using the release or prerelease version of reaticulate?

_Stevie_ · 03-04-2021, 06:21 PM

Great!
Using Reaticulate 0.4.6, here.
I will send you a video I did for a friend, where I tried to trigger the behavior!

Justin · 03-04-2021, 06:57 PM

Got the video. Really having trouble duplicating. :/ Any way you could go tell me what released version it started with? 6.20? 6.19? (It's possible it was 6.21-6.23 but I think it's pretty unlikely).

_Stevie_ · 03-04-2021, 07:08 PM

I started having troubles on a project on February 16h. So my guess is, the dev needs to be around that date.
I’m currently using 6.21 dev202a which works totally fine. I can work my way towards the build that causes the issue, tomorrow, if that helps.

Justin · 03-04-2021, 07:36 PM

Quote:

Originally Posted by _Stevie_

I started having troubles on a project on February 16h. So my guess is, the dev needs to be around that date.
I’m currently using 6.21 dev202a which works totally fine. I can work my way towards the build that causes the issue, tomorrow, if that helps.

Thanks, that would be helpful! If you could start with the release versions first that would be best, too.

_Stevie_ · 03-04-2021, 07:37 PM

I couldn't wait til tomorrow... haha. I'm just going thru them, right now.
Will report back in a bit.

_Stevie_ · 03-04-2021, 08:19 PM

So, I have no issues with v6.23+dev0205 - February 5 2021.
I hammered it for 30 minutes and couldn't get it to crash.
That means, v6.23+dev0206 - February 6 2021, is the first version that
makes the project crash.

@o_ciz: could you give v6.23+dev0205 a spin, if this solves your issue?

Justin · 03-04-2021, 08:25 PM

Quote:

Originally Posted by _Stevie_

So, I have no issues with v6.23+dev0205 - February 5 2021.
I hammered it for 30 minutes and couldn't get it to crash.
That means, v6.23+dev0206 - February 6 2021, is the first version that
makes the project crash.

@o_ciz: could you give v6.23+dev0205 a spin, if this solves your issue?

Thanks! That gives me a lead...

_Stevie_ · 03-04-2021, 08:35 PM

You'we welcome, I hope it helps. Looking at the changelog for

Code:

v6.23+dev0206 - February 6 2021
  # ReaSurround2: draw shadows under inputs in top view

didn't reveal many fundamental changes. I hope there was more under the hood
and that you are able to figure it out. Fingers crossed!

Justin · 03-04-2021, 10:17 PM

Quote:

Originally Posted by _Stevie_

You'we welcome, I hope it helps. Looking at the changelog for

Code:

v6.23+dev0206 - February 6 2021
  # ReaSurround2: draw shadows under inputs in top view

didn't reveal many fundamental changes. I hope there was more under the hood
and that you are able to figure it out. Fingers crossed!

Got it! Should be fixed in the next build and 6.25 in the next few days.

_Stevie_ · 03-05-2021, 05:18 AM

Aweeeeeesome, thanks Justin!!!
Out of curiosity: care to elaborate what caused the issue?

o_ciz · 03-05-2021, 08:38 AM

Quote:

Originally Posted by _Stevie_

So, I have no issues with v6.23+dev0205 - February 5 2021.
I hammered it for 30 minutes and couldn't get it to crash.
That means, v6.23+dev0206 - February 6 2021, is the first version that
makes the project crash.

@o_ciz: could you give v6.23+dev0205 a spin, if this solves your issue?

Yes I can confirm that version 6.23+dev0206 is the first one to feature this bug. I am currently running 6.23+dev0205 without problems.

Justin · 03-05-2021, 10:12 AM

Quote:

Originally Posted by _Stevie_

Aweeeeeesome, thanks Justin!!!
Out of curiosity: care to elaborate what caused the issue?

There were some internal memory use cleanups in EEL2/JSFX, one of which broke stack_*(). Totally my fault. :/ 6.25rc1 will be along shortly which should fix, and 6.25 in the next 24 hours (fixing a few other bugs too).

o_ciz · 03-05-2021, 10:41 AM

Quote:

Originally Posted by Justin

There were some internal memory use cleanups in EEL2/JSFX, one of which broke stack_*(). Totally my fault. :/ 6.25rc1 will be along shortly which should fix, and 6.25 in the next 24 hours (fixing a few other bugs too).

Awesome. Reaper devs are the best.

Justin · 03-05-2021, 10:52 AM

6.25rc1 is up!

_Stevie_ · 03-05-2021, 12:02 PM

Thanks for those insights Justin. And thanks for fixing so ultra fast!

tack · 03-05-2021, 05:44 PM

Quote:

Originally Posted by Justin

There were some internal memory use cleanups in EEL2/JSFX, one of which broke stack_*(). Totally my fault. :/ 6.25rc1 will be along shortly which should fix, and 6.25 in the next 24 hours (fixing a few other bugs too).

Great to know that I'm not doing anything janky in the JSFX.

(Well, at least related to this crasher, anyway.)

Thanks for turning around a fix and thanks especially Stevie for spotting and reporting it.

_Stevie_ · 03-05-2021, 10:00 PM

Happy to help, although o_ciz was the first one to point this out here in the thread. I only jumped in and provided as much data as I could

Really happy this got fixed so quickly!

tack · 03-05-2021, 11:07 PM

Oops, quite right, thanks o_ciz