High RAM usage since last update?

[plasticfractal]

is anyone else having this issue? Since the last update, Reason will keep using more and more RAM, even if I just have a few devices in a project and no audio. over time it actually struggles to play music because it's using up like 15 gigs of my RAM. I never had this problem before the latest update. I'm in Windows 11, and this happens even if I have a simple project open for a while.

[antic604]

is anyone else having this issue? Since the last update, Reason will keep using more and more RAM, even if I just have a few devices in a project and no audio. over time it actually struggles to play music because it's using up like 15 gigs of my RAM. I never had this problem before the latest update. I'm in Windows 11, and this happens even if I have a simple project open for a while.

I remember one of the versions had a problem with memory leak, i.e. it would use more & more memory as time passed. But it has been fixed and I've not noticed it in current version (I only have 8GB of RAM).

Perhaps it's a specific plugin or RE that you're using?

[Loque]

I compared it with R11 and R12 on 140% zoom. Not much of a difference.

Note, that if you f.e. add a Piano as RE or any other sample library, it consumes easily 3GB RAM. Add a few more instruments of that kind and you are at the 15GB.

[Rising Night Wave]

huh, i did not know that.
thanks for informing us.

[wereMole88]

Which version had the high RAM usage?

[fullforce]

is anyone else having this issue? Since the last update, Reason will keep using more and more RAM, even if I just have a few devices in a project and no audio. over time it actually struggles to play music because it's using up like 15 gigs of my RAM. I never had this problem before the latest update. I'm in Windows 11, and this happens even if I have a simple project open for a while.

How much RAM do you have? If the answer is 16, that's bare minimum nowadays.

[Przemyslaw]

I have similar issue. Load project today with few (4-8) audio tracks and few sampled instruments (piano, strings), some synths and mass of effects plugins, at the beginning Ram usade reaches 23GB, after 20-40min Ram usage drops to 6GB. This isn't the first project I've noticed this. "Song optimization" does not help. I have 32GB of RAM and when opening reason projects the usage reaches over 90%.
Windows 10. Maybe it's a bit of a Mac approach, i.e. using all available RAM in the device.

[jam-s]

It could be the indexing task running in background and building the sample database.

[mind2069]

I have similar issue. Load project today with few (4-8) audio tracks and few sampled instruments (piano, strings), some synths and mass of effects plugins, at the beginning Ram usade reaches 23GB, after 20-40min Ram usage drops to 6GB. This isn't the first project I've noticed this. "Song optimization" does not help. I have 32GB of RAM and when opening reason projects the usage reaches over 90%.
Windows 10. Maybe it's a bit of a Mac approach, i.e. using all available RAM in the device.

I have started a thread a month ago complaining about this exact issue with Reason 12

I had 16GB and getting out of memory (95%), upgraded to 32GB still getting to 90%, now I'm at 64GB ram and again getting 90% (all the exact same song) and after 20 minutes, not even touching the computer, the memory drops to 15 to 20 GB, with 64GB, at least I'm not getting out of memory even when it reaches near 100%.

[mind2069]

I have similar issue. Load project today with few (4-8) audio tracks and few sampled instruments (piano, strings), some synths and mass of effects plugins, at the beginning Ram usade reaches 23GB, after 20-40min Ram usage drops to 6GB. This isn't the first project I've noticed this. "Song optimization" does not help. I have 32GB of RAM and when opening reason projects the usage reaches over 90%.
Windows 10. Maybe it's a bit of a Mac approach, i.e. using all available RAM in the device.

I have started a thread a month ago complaining about this exact issue with Reason 12

I had 16GB and getting out of memory (95%), upgraded to 32GB still getting to 90%, now I'm at 64GB ram and again getting 90% (all the exact same song) and after 20 minutes, not even touching the computer, the memory drops to 15 to 20 GB, with 64GB, at least I'm not getting out of memory even when it reaches near 100% in the first 20 minutes.

[Przemyslaw]

I have started a thread a month ago complaining about this exact issue with Reason 12

I had 16GB and getting out of memory (95%), upgraded to 32GB still getting to 90%, now I'm at 64GB ram and again getting 90% (all the exact same song) and after 20 minutes, not even touching the computer, the memory drops to 15 to 20 GB, with 64GB, at least I'm not getting out of memory even when it reaches near 100% in the first 20 minutes.

So, this at least explains that the solution is not to buy more RAM.

[Hazel]

That doesn't sound right. I have 16gb ram and I've never hit the ceiling yet with even very elaborate projects. That being said though, I'm still on R11.... No idea how much they have changed internally for 12, so maybe it's just much more intensive...no idea. Even back when I was on the newest one, I would hold off on point updates for a long time before finally trying it out...just in case.

[mind2069]

So, this at least explains that the solution is not to buy more RAM.

Read again (64 GB, at least I'm not getting out of memory even when it reaches near 100%)

[Przemyslaw]

now I'm at 64GB ram and again getting 90% (all the exact same song)

I don't have "out of memory" info with 32GB.

[Theo.M]

Just bumping this as I am having issues with Waves plugins.

Recently I was trying out BB Tubes in place of a tape plugin at 8x OS and very mild settings to see how it sounded on ever track, and when I'd load the reason project of 70 ish tracks it would use my entire 64GB ram and the Waves were practically the only plugins in the project!

I have been writing to waves saying it's broken, but it's reason...

I tested other DAWs and even up to 200 instances lol and the entire lot use 1GB on other DAWs, so something is seriously wrong here. If Reason is the only one with the issue, it points to Reason, yes?

[Przemyslaw]

Reason have problem with vst3, usually need 500MB of RAM for one instance of plugin. More info in this thread:
viewtopic.php?f=48&t=7530035&p=659132#p659132

[ProfessaKaos]

I've also noticed a lot of RAM being used by Reason 12. I load up a song which has a fair bit going on within it and it will use about 40-50GB of the 64GB's my system has.

[ProfessaKaos]

Reason have problem with vst3, usually need 500MB of RAM for one instance of plugin. More info in this thread:
viewtopic.php?f=48&t=7530035&p=659132#p659132

Thanks for this, I believe this is what I'm experiencing.

[Theo.M]

Reason have problem with vst3, usually need 500MB of RAM for one instance of plugin. More info in this thread:
viewtopic.php?f=48&t=7530035&p=659132#p659132

Wow ok, that's what it is. What a shame!

Surely RS consider this an official bug?

Still haven't installed on Mac, do you know if the issue is there too? I guess Reason can't use AU?

[Theo.M]

Wow, this is crazy!
I created an audio track with same Waves BB Tubes plugin but the *VST2* version this time.
I then duplicated it 127 times for 128 tracks.

With VST3, this uses my entire system ram of 64GB.

With VST2 of the same plugin, a total of 1.8gb is used.

This is really serious, and for even medium sized projects, but especially large ones, it makes VST3 in Reason unusable even for people with an 128GB ram dream machine!

So please, AVOID VST 3 in Reason right now, at least on Windows 11, that's for sure. I will check Mac soon.

[Popey]

Let's hope they get this fixed seeing as any new vsts will most likely be vst3 option only (no vst2)

[MirtazapineDream]

I wonder if they're silo-ing the whole VST binary into RAM for the sake of performance/compatibility with the rack. If the VST needs to have all of its code exposed for APIs to work when wiring in and out of the VST in the rack. Just a thought, and a terribly uninformed one at that.

[Theo.M]

I don't think this was in any way a conscious decision.

Think about it.

If someone has 16gm ram, it would be impossible to do a 32 track project in Reason using VST3 plugins on every track. Where as with any other VST3 host it would be absolutely fine.

So there's no way that sort of oversight was even remotely noticed in beta testing IMO or they would have delayed the release. Basically it's actually broken.. And these days I really do not say that lightly at all, and if anything they should currently do a hotfix to *disable* VST3 support.

[robussc]

Thought I'd do a sanity check here on my MacOS machine, three VST 3's loaded and powered up

Monosnap untitled 2024-04-11 15-21-30.png (808.38 KiB) Viewed 499 times

[Theo.M]

Thought I'd do a sanity check here on my MacOS machine, three VST 3's loaded and powered up

Monosnap untitled 2024-04-11 15-21-30.png

Definitely better than Windows, so maybe it's not happening on OSX.