Using up all the RAM??

I’m currently using v18.1.3 and am seeing a lot of cautions due to RAM usage and almost all of it is from DR. I was doing some simple work in Fusion. Very basic stuff. I shut down DR after getting this latest message, restarted DR, and went back into my work while monitoring RAM usage. The usage was very low this time.

I’ve had lots of issues recently with regards the RAM usage across a host of different projects.

Is this a known bug?
Are many others reporting this issue?
Will there be an update issued to address this?

UMMMMMMM ..... So, I'm the only one in the world that is seeing this problem??

Yesterday, my computer flagged the RAM warning as DR was using about 120Gb.
No one is seeing this same problem???
Is there a fix?

Regards,

If you haven't done so already, try limiting RAM usage in Resolve and Fusion by adjusting the sliders in User Preferences, under the System Tab I believe. That could help free up your RAM for other applications and once Resolve hits it's limit, it should start overwriting its previous RAM usage. Resolve is great in the sense that it will use all the RAM you throw at it—which is a behavior super-users seek out. It's really annoying when you have a beefed out system with a lot of available RAM that you want to be used, but a program just isn't optimized to use everything; especially when you spent money on upgrading a workstation to have more RAM. Not a bug, but I think in your case limiting the RAM by changing the setting will help with any concerns you might have.

Sent from my motorola razr using Tapatalk

Fusion Cache would always use lots of ram if you let it. I don't think this is a change in recent versions.

Are you using fusion?

I am 100% certain that the problem is a memory leak.
Yes, I’m using Fusion BUT just doing very very basic things; masks and such.
Only working with tiny clips, testing keying and masking methods.
No other apps are running.
While monitoring the RAM, it starts near 30Gb then climbs past 100Gb with almost no changes. It’s annoying.

In other words, something somewhere is definitely wrong with this version. I can set RAM limits but that is not a solution. My goal is to notify Blackmagic, have them pool the complaints, search for the cause, apply a solution, and roll out a fix.

In other words, something somewhere is definitely wrong with this version. I can set RAM limits but that is not a solution. My goal is to notify Blackmagic, have them pool the complaints, search for the cause, apply a solution, and roll out a fix.

Send a support email, they will give you a ticket number and may ask for more details.

Not sure if they ever actually notify anyone when they fix the tickets. I have like 3 and never heard anything back.

[Peter Chamberlain]

Without a repo and logs it’s unlikely we could fix it as we can’t see it.

Without a repo and logs it’s unlikely we could fix it as we can’t see it.

I’d be happy to send you whatever you need but I don’t know what “repo” means. I can create a log file, though.

[Peter Chamberlain]

We would need info how to reproduce the issue.

Not seeing the issue on my Mac.

Neither here.

Okay, thanks for information. It might be isolated to just one project and I’ll deal with it.