Resolve Studio 18.1 running out of GPU & vanishing

Hi,

I have a Dell XPS 15 9510 laptop with 64Gb memory, 16 CPUs core, and 2 GPUs (Intel UHD graphics and NVIDIA GeForce RTx 3050 Ti laptop with 4Gb memory).

I have an hour-long timeline with 1920 x 1080 footage and am trying to render the cache.

Resolve vanishes (crashes) with no warning on Windows 11. The Windows event log says ...

An application has requested more GPU memory than is
available in the system.
The application will now be closed.

Error code: 6
(pid=16456 tid=32276 resolve.exe 64bit)

As you can see from the screen grab, the GPU saw tooths, which is fine, but then it doesn't and Resolve crashes.

Screenshot 2022-11-23 112426.png (215.77 KiB) Viewed 1059 times

My computer is pretty well specced and the video isn't long or complex, so this seems odd? There are no large images.

I have the latest drivers (526.98 NVIDIA)

Any help much appreciated - thanks!

Same here - I got a Dell Precision 5550 with 64Gb of Ram, Intel i7-10875H CPU, NVIDIA Quadro T2000 4Gb.

With Davinci Resolve 17 - I had no issues at all, and can render away with no crashing whatsoever.. Since I've upgraded to Resolve 18 - I can't render.. It will always crash with an

"Nvidia OpenGL Driver" error.
An application has requested more GPU memory than is available in the system.
The Application will now be closed.

Error code 6

Updated the nvidia drivers to 526.67, same thing. Installing Resolve 17 - no issues.. Please fix! Love the new features in Resolve 18!

[Peter Chamberlain]

Change the GPU driver

4Gb VRAM should be enough for most FHD work.
But it is a serious limitation of both your systems.

Change the GPU driver

But I have the latest GPU driver? At the very least, Resolve should give a warning, and not just simply vanish?

4Gb VRAM should be enough for most FHD work.
But it is a serious limitation of both your systems.

I'm not doing very complicated work, and I'd suggest that Resolve shouldn't simply crash. Give a warning, or run slower, sure.

Agreed, however, this suboptimal handling of low GPU memory has been occurring in the product for years. I've heard it has something to do with the driver not reporting the available memory correctly. Some versions of the driver have been more graceful than others. Plus it seems that version 18 uses a bit more GPU memory than version 17 (based on what others have reported).

The picture of task manager above shows that it went to 4Gb. So it means it was really consuming that value.

So maybe turn off other stuff: like a browser for example. How much VRAM was using without Resolve?

The picture of task manager above shows that it went to 4Gb. So it means it was really consuming that value.

So maybe turn off other stuff: like a browser for example. How much VRAM was using without Resolve?

Hi Alex,

It uses pretty much no GPU without Resolve - everything else is closed down. I've changed the caching settings so it's not crashing more though.

Neil

Never bevore got this message:

GPU memory is full...

but since 18.1.1.

Resolve is closing then.

I do nothing else than before.

I'm pretty sure there's some sort of GPU memory leak in 18.1.1 - when I have the render cache set to 'smart' it just goes up and up and up, whereas I'm guessing it should occasionally garbage collect / free up memory. When I have it set to 'user' it saw-tooths and then crashes.

I'm pretty sure there's some sort of GPU memory leak in 18.1.1

That issue has been around for several versions.

I've never seen an acknowledgement from BMD on the issue, so it may never get fixed.

Ah! Well, fingers crossed ...

I'm pretty sure there's some sort of GPU memory leak in 18.1.1

That issue has been around for several versions.

I've never seen an acknowledgement from BMD on the issue, so it may never get fixed.

I'm pretty sure there's some sort of GPU memory leak in 18.1.1

That issue has been around for several versions.

I've never seen an acknowledgement from BMD on the issue, so it may never get fixed.

You are probably right. I noticed that on the tail end of DR 17. VRAM is never purged and at the end it's just unusable. Most of the time a simple restart will suffice but that's really annoying....