Memory Leak with Anticipative FX Processing (FIXED)

[innuendo]

Basically this is the same bug as referenced here:
http://forum.cockos.com/showthread.php?p=1409140

And here's the issue on the deprecated issue tracker:
http://forum.cockos.com/project.php?...55#attachments

I decided to open a new thread since this bug changed slightly with Reaper 5, and because I think I have better understanding of conditions under which it is triggered now.

To reproduce:
1) Turn Anticipative FX ON and make sure Render-Ahead is set to at least 200ms (it will also show up with shorter lengths but will be harder to reproduce)
2) Open the attached project
3) Start playback
4) Stop playback close to the loop's edge, while monitoring memory use

Notes:
- I tested this on Windows, don't know whether this bug applies to Mac OS X
[Edit: cfillion confirmed this on OS X with render-ahead set to > 2000ms]
- This bug requires a project with at least 2 tracks, and a send from Track2 to track1. The send can be enabled or disabled, it doesn't matter.
- This bug requires an FX on Track2. The FX can be bypassed or disabled, it doesn't matter.
- This bug only happens in loop mode and when the loop is sufficiently short. With longer loops (I tried about 15mins), it will start the same but after a while will free the RAM.
- This bug only happens when the selection ends at least 16 min or so into the project time.
- With shorter buffer lengths set in the audio interface properties, memory leaks faster. About 3x faster with 64 samples than with 1024 samples.
- The more FX you have on that track, the easier it becomes to trigger the bug. With enough FX, it doesn't matter where you stop the playback.
- As soon as you move the playback cursor, leaked memory will be instantly freed

[cfillion]

I can't reproduce the leak on OS X. I tried adding 15 FXs to the second track, setting the buffer size to 64 and with these Anticipative FX Processing settings: https://i.imgur.com/4GHPWLb.png.
The memory usage stays constant at around 48 MB.

EDIT: Never mind, it's leaking on OS X too with render-ahead set to >2000ms like @snooks said below.

[snooks]

Confirmed here on Win 10 x64. I am getting it happening when I stop within ant-FX buffer length of the loop end. Testing with 40 FX on track 2 here. It's easier to check the behaviour with ant-FX set to 2000ms or so.

edit: # of FX is irrelevant here. Just need to stop within ant-FX of loop end.

[ELP]

Yes i can reproduce this with v5.02.
If you Stop right..... then during Stop the memory consumption increases continously until nothing goes anymore.

If you press Start again, leaked memory will be instantly freed.
But it is true; as long as you are in Stop mode: the memory consumption increases continously..

That means, stop and go away to drink one or more cups of coffee is maybe not a good idea.

This is clear a bug.

[innuendo]

Thanks for confirming guys.

While a 3MB/s leak might not sound like anything dangerous, if you duplicate Track1 a few times (or just work with a real-life complex project longer than 16 minutes and use loops), you get dozens or even hundreds of MB blasting your RAM in seconds.

[ramses]

Have you reported this in the pre-release forum? How far back does it happen?

[innuendo]

This is not a pre-release bug, it affects stable versions as well. I started using Reaper when it was in v4, and I think it was there since the beginning, but it took me a while to narrow down on it. Anyway it affects also 4.x, but I can not say for sure when it was introduced.

[Justin]

Thanks, this will be fixed in the next version (5.03)!

[innuendo]

Originally Posted by Justin

Thanks, this will be fixed in the next version (5.03)!

Yay!!!

[nofish]

5.03pre1 with the fix is up for testing

[innuendo]

Fixed in the latest beta!