Page 1 of 1

GPU Memory Full, v17

PostPosted: Sun Mar 21, 2021 2:59 am
by gprhodes
I am running into a GPU Memory full error in Resolve Studio 17. I have about 16 minutes of multiple video clips in my timeline, all 1080p, almost no corrections or other changes at this time. I'm on a Surface Book 2, with a NVIDIA GeForce GTX 1050 having 2gb of dedicated memory and another 8gb available from RAM.

I get the error just trying to add a jpg photo to my media library.

Suggestions for solving this problem?

Re: GPU Memory Full, v17

PostPosted: Mon Mar 22, 2021 2:54 am
by Peter Chamberlain
What is the resolution of the JPEG?

its likely the GPU is downrezing it to the timeline res and using all the listed ram.

Re: GPU Memory Full, v17

PostPosted: Tue Mar 23, 2021 3:44 am
by gprhodes
Peter Chamberlain wrote:What is the resolution of the JPEG?

its likely the GPU is downrezing it to the timeline res and using all the listed ram.


It's a 4mb file.

Re: GPU Memory Full, v17

PostPosted: Tue Mar 23, 2021 5:45 am
by Peter Chamberlain
Ok, but what is the resolution?

Re: GPU Memory Full, v17

PostPosted: Tue Mar 23, 2021 3:36 pm
by gprhodes
8196x5879, 1200dpi.

Re: GPU Memory Full, v17

PostPosted: Wed Mar 24, 2021 1:53 am
by Uli Plank
Probably too much for 2 GB VRAM. BTW, dpi doesn't matter for video, pixel count is it.

Re: GPU Memory Full, v17

PostPosted: Wed Mar 24, 2021 9:40 pm
by gprhodes
Thanks. I'm coming from the still photo world and still pretty new to video & its editing.

Re: GPU Memory Full, v17

PostPosted: Thu Mar 25, 2021 1:20 am
by Marc Wielage
gprhodes wrote:I am running into a GPU Memory full error in Resolve Studio 17. I have about 16 minutes of multiple video clips in my timeline, all 1080p, almost no corrections or other changes at this time. I'm on a Surface Book 2, with a NVIDIA GeForce GTX 1050 having 2gb of dedicated memory and another 8gb available from RAM.

I think it's going to be extremely difficult to run Resolve with this little RAM and this little VRAM. It can be done on a full-fledged laptop, particularly a high-powered model that's a desktop replacement (with lots of RAM, multiple CPU cores, and a decent GPU). My opinion is that Resolve will be problematic at best on a tablet PC.

Re: GPU Memory Full, v17

PostPosted: Thu Mar 25, 2021 1:52 am
by Uli Plank
While I generally second that, he should be OK with some editing and limited grading in HD.
It might be helpful to reduce the timeline resolution to 1280x720 while editing and switch it to HD before rendering.

But careful testing is needed to avoid disappointments after preparing a lengthy project!

Re: GPU Memory Full, v17

PostPosted: Tue Mar 30, 2021 10:05 am
by Paul Vanezis
Just an observation from a project I have been working on for the last 6 weeks. I started with Resolve 16 and updated to 17 last week. I had a few issues with memory management but I was able to work through those issues and can continue... until this morning.

I did a small amount of work in a different project; Dustbuster work. I have live save on and Resolve just stopped, then shut down. No warning. In fairness it does this every now and then and I am working with 4K scans from the Cintel scanner.

I decided to continue with that project later, then opened my 6 week old project to continue. This also uses 35mm 4K scans from the Cintel scanner. Immediately I was getting GPU full errors and I could do no work in the project.

My system is:
Processor - i9-7900X
GPU - Nvidia GTX 1080 Ti (11GB RAM)
System Memory - 32GB RAM

I tried everything but still got the error warning. After going round in circles, I went into Task Manager and discovered three instances of Resolve running, all of which were using system resources. When I closed Resolve, two of those instances were still running. I ended those processes and restarted Resolve. All is now back to normal.

I suspect that this isn't a software issue, but to do with how systems with different configurations close processes that are memory intensive.

This may not be an issue affecting those that see this error but it may be worth checking active Resolve processes running if you get this warning. It would certainly explain why systems generally work fine on a machine reboot but don't if Resolve has to be restarted without one.