DAW gets unstable after being up a while

[AudioWonderland]

I am finding that if I am working in a project for a few hours (say at least 3hrs) that things start to get glitchy, audio will not play correctly and eventually Reaper will crash.. A reboot fixes the issue. Restarting Reaper does not. I only use this machine for Audio/Reaper. Not sure if this is a Reaper issue, Hardware issue or some third party app but since restarting Reaper does not correct it, I suspect its not that.

Its about 5 years old, i7 processor, 48gb RAM. I don't do a lot of VI but I have slate drums and 2-3 Sampletank 3 instances running in this particular project. Not sure where to start with this.

[EpicSounds]

Since it is an older system I would guess dust collection impacting cooling.

Maybe worth checking RAM
https://www.howtogeek.com/260813/how...-for-problems/

[AudioWonderland]

Originally Posted by EpicSounds

Since it is an older system I would guess dust collection impacting cooling.

Maybe worth checking RAM
https://www.howtogeek.com/260813/how...-for-problems/

Good thought, but I was just in the box. I did not note any dirt or other contaminants that would be an issue.

[mpi]

The same happens to me. Started a few versions ago. Playback becomes sketchy. Pauses in the middle of playback. Lots of pops and clicks. Eventually crashes and only a reboot fixes it (unkillable Reaper process).

I noticed that the RAM goes up during this, so assumed a memory leak that's writing to parts of memory it shouldn't in which case the developers should catch it themselves if that's what's really happening.

Reaper used to be rock-solid beforehand.

[beingmf]

Sounds like a memory leak in one or several plugins. Which ones are you using on a regular basis?

[AudioWonderland]

Originally Posted by beingmf

Sounds like a memory leak in one or several plugins. Which ones are you using on a regular basis?

Mostly waves Comps/EQ's, Echoboy and Sunset Sound Reverb

[karbomusic]

I'd look at how much memory it's actually using before saying it's a memory leak. And a memory leak shouldn't cause glitches per se but not out of the question.

To the other user's mention of unkillable process, that's not a memory leak but with the driver and kernel where reaper.exe is stuck waiting on something down in kernel that isn't there anymore (or similar). That's why it's not killable without a reboot which reboots the kernel in the OS. Also, typically writing to memory one shouldn't should result in pretty much an instant crash (access violation) or corruption that causes a crash a short time later.

Are the drivers up to date as a sanity check? I also wouldn't hesitate to think it's one of the plugins misbehaving - I suppose you could run those in a separate process (a reaper option) and when it happens again, reaper should still work but the plugin will be fubar on its own in it's own separate process.