02-08-2020, 10:49 AM
(This post was last modified: 02-08-2020, 11:16 AM by Mattias Westlund.)
(02-08-2020, 06:24 AM)Samulis Wrote: Thanks for sharing this! Certainly there must be others out there who have had this issue.
I wonder if there's a memory leak with the interaction between Reaper and Windows 10. Very strange that a feature promising one thing results in causing the opposite to occur!
That was kind of my thinking as well. Maybe an update to Windows changed something in the way RAM compression interacts with some programs. I really doubt that REAPER itself has a memory leak. I've been on v 4.78 for years now and I'm sure I would have noticed it before.
Edit: Here's a thought. Maybe REAPER somehow doesn't "see" that Windows is compressing memory and only notices that RAM usage is rising to unsafe levels? I mean, perhaps it only knows how much RAM it allocates to begin with and has no idea what Windows does with it afterwards, if that makes sense.
Edit 2: That still doesn't explain why the projects seem to use more RAM with compression on, though.
