Reaper crashing on low memory.

Is there any way to make how Reaper handle running out of memory a bit more graceful? It's making me paranoid, I'm always on the verge of exceeding the (retarded) limit of physical memory, so I never know when Reaper is gonna go "poof" on me. There has to be a way, the other programs I run do slow down to a crawl when I exceed the 2 GB limit, but they don't suddenly go poof...

is THAT what causes the poofing? Its killing me

Well yeah, it's been a long standing thing with Reaper. The answer in older days was to add memory to the system, but you can't do that when you've reached the limit of 32 bit system. And there really isn't any workaround, if you're on the threshold and you try to bounce, the simple act of bouncing will overload your memory and Reaper will go poof.

agreed - but, just out of interest, what sort of sessions are you running that are sucking that much RAM? i've only ever noticed this with buggy plugins. i rock some pretty giant sessions, but always run out of CPU waaaaaaay before i go anywhere near the RAM limit.

Yes totally, perhaps some mechanism that tells you to click 'OK' to undo the action it was doing that's eating the memory. Assuming it isn't easy for REAPER to check the memory requirements of what it's loading before loading it - doing so whilst loading it and offering some sort of escape route would be great and is needed really...

I have the same problem. Reaper just suddenly goes "poof!" back to the desktop. This is usually when running several instances of Nebula, which means it is most likely memory related as it uses huge chunks of it. Cheers! bManic

Yup I have this too, mainly when running Omnisphere - a memory hog. REAPER often gives me a runtime error before dying.

I get this with no plugs, just when my rpp gets to megabytes size and tons of edits

This is driving me nuts... I posted this earlier: I think I've pretty much hunted down all the bugging plugins and the system seems to be rock solid until it reaches the the memory usage of 1,1-1,2 gigs. My Windows and Reaper sees 3,25 Gigs of available memory. This current project seems to be a bit too much though. Track count is something like 180 including sends, groups and folder tracks which I use a lot. FX count is currently around 230, no midi or sample based "memory hog" plugins. CPU usage is around 60-80%. Crashes in about every 5 to 20 minutes. Usually the session opens fine but after working a while a start to get plugin GUIs with dropped images (indicates a memory thing?). Other than that Reaper is fully responsive all the time before crash. The most usual situation when crash happens is when I start playback or zoom in with mousewheel. Is there a way to customize how much Reaper allocate memory for different part of the program? Could I someway experiment different settings so Reaper would use less memory?

This is an old thread of mine: I think it could be related to your issue. Read posts n.17 and n.18