RAM decommit pattern

Hi

I'm not sure if this is a known bug, but when closing Resolve after having viewed many long files, RAM is decomitted (aka deallocated) in a particular pattern.
It's also reeeally slow, the time it took to finally close Resolve is 7 minutes

Is anyone else seeing this?

Yes I do see this.
Also I noticed that Resolve uses way more ram than before (started a few versions ago).

I have more than enough ram, so I don't care, but that decommiting thing is really strange.

I thought windows only emptied memory if you needed it. At 13% you've got plenty of empty memory.

Think of it this way. You exit. A second later start the program again. Would it have made sense to have released all the memory and to reload it now?

Either way I doubt that's a Resolve issue. It's Microsoft .

I thought windows only emptied memory if you needed it. At 13% you've got plenty of empty memory.

Think of it this way. You exit. A second later start the program again. Would it have made sense to have released all the memory and to reload it now?

Either way I doubt that's a Resolve issue. It's Microsoft .

No. it's the following: I exit. I wait 7 minutes for Resolve to stop using memory. I start resolve.

It's definitely a Resolve problem as it's the program cleaning up after itself after I click the close button.
And it's 13% after resolve has completely shut down.
But more importantly than the actual numbers, look at the damn graph: It goes up then down then up then down.

I would like to ask you 2 questions:
1. Why do you think this is Resolve problem?
2. Why do you think this is a problem at all?

I would like to ask you 2 questions:
1. Why do you think this is Resolve problem?
2. Why do you think this is a problem at all?

1: Because other programs can exit instantly. Just today I played some Cyberpunk 2077. It went from 24 GB commited to 13 GB in 3 seconds.
And I happen to know that there's a bunch of memory allocators: macolloc(), phkmalloc() etc: https://github.com/emeryberger/Malloc-I ... allocators for some of them

2: Because I don't want to wait 7 minutes for Resolve to decommit each time I restart.

Could be something on your system? I tested with three 25 GB files (i got 64 gb ram) and the decommit took 2 seconds after i closed DVRS. I don't use project dynamic switching btw.

Could be something on your system? I tested with three 25 GB files (i got 64 gb ram) and the decommit took 2 seconds after i closed DVRS. I don't use project dynamic switching btw.

I doubt it.
Same pattern in two different systems. Both studio and free.

Breakthrough:
It only happens when I close Davinci and have Decode options -> Decode H.264/H.265 using hardware acceleration AND NVIDIA ticked.
When NVIDIA is not ticked, davinci decommits instantly.