BUG: Runaway Mem Rendering/Playing prj w/JPG if Video Acceleration On

RedRob-CandlelightProdctns wrote on 3/10/2023, 2:31 PM

BUG: Rendering a project with JPG as part of composite causes runaway RAM when NVIDIA GPU is enabled under "hardware acceleration" NOTE: Revealed in 1st 2 comments below, same problem when just playing a project w/JPG and GPU enabled.

This has been a bug for a long while now -- I made a video demonstrating the problem; maybe it will help get it squashed? It is very easy to reproduce.

Synopsis of that demo video

With hardware accelerated video enabled, render a small project that include a not-tiny JPG file. Add other elements so the render takes a while. Observing memory usage in Task Manger you'll observe it climbing higher and higher throughout the render until the render completes or it crashes from no more memory.

Turning off hardware accelerated video, render the same project and observe memory usage. It remains constant throughout the render, with no issue.

Comments

Todd-A0 wrote on 3/10/2023, 5:08 PM

If you loop playback on timeline does the same thing happen?

RedRob-CandlelightProdctns wrote on 3/10/2023, 10:38 PM

@Todd-A0 YES!

Same project, I just played/looped the region and watched memory use climb from 40% (where it started) to 58% until I stopped it after a few minutes. When I started playing again I watched it (via task mgr) continue climbing from 58% to 61% and going.

I'll update the description of the thread if it lets me.

RedRob-CandlelightProdctns wrote on 3/10/2023, 10:51 PM

I first reported this hear on Vegas 17 in January 2020. I observed it as a problem with both .PNG and JPG files.

https://www.vegascreativesoftware.info/us/forum/runaway-ram-when-using-gpu-for-render-vegas-error-vs-gpu-driver--118430/

RedRob-CandlelightProdctns wrote on 3/10/2023, 11:00 PM

OK. More info... if there are two tracks has a PNG and a track under it has a JPG, the runaway RAM occurs. If I remove EITHER the .png track OR JPG track, memory does not run away!

RedRob-CandlelightProdctns wrote on 3/10/2023, 11:09 PM

As requested in 2020, here's a ZIP file containing three things.

.VEG project file, with three tracks (text track, PNG track, JPG track)
a 194KB transparent PNG
a 472KB .JPG file

Playing the project in the timeline with GPU accel. video enabled causes RAM to just keep going up, as observed in task manager. Disabling GPU accel and everything is normal.

https://www.dropbox.com/s/le5bbwjqpeey1nm/runaway-ram-with-png-and-jpg.zip?dl=0

RogerS wrote on 3/11/2023, 2:14 AM

Interesting. I tested with my desktop (see signature). With VP 20 I let it playback the project in a loop and after 12GB it was very slow with the increase- a few passes for .1GB. I then did a render (1080p MagixAVC) and it went up to 13GB but then dropped to 10GB after the render finished.

I then copied and pasted the events 4x to make it longer and quickly got to 12.6GB ram usage. As soon as I started a render it dropped back to 10.x and stayed there (no increase during the render).

I am doing a loop test with the 5x events and it's not going above 12.8GB.

A few things with this project; it uses a non-native NewBlue transition which I don't have. None of the text events or images are quantized to frame boundaries- enable both options under options/quantize to frames.

john_dennis wrote on 3/11/2023, 9:40 AM

@RedRob-CandlelightProdctns

I looped multiple instances of this project while I worked with pictures in Photoshop and the memory usage stayed flat.

I don't have New Blue on this machine.

I don't have your machine.

Pet Peeves

Unquantized frames give me agida. I've been known to go back and move audio cuts to frame boundaries on old projects.
There is no reason to have a deinterlace method set for progressive source.
Resample Mode could be set to Disable Resample since nothing in this project has a frame rate.

RedRob-CandlelightProdctns wrote on 3/11/2023, 10:09 AM

@RogerS so yours rose more than one might expect but then stabilized, ya?

@john_dennis I'm surprised to see only Intel video card considering your high-RAM and CPU stats! What is your video acceleration set to in Vegas?

I did not notice a NewBlue effect in there.. I will remove it and repeat the test.. prob was a transition originally and then I removed the edge fades. I usually disable resampling and deinterlacing may bug you here but it just won't do anything (no footage) so.. pppppth

If an event is shifted off-frame, did it take a... quantize leap? 😏

Reyfox wrote on 3/11/2023, 11:09 AM

@RedRob-CandlelightProdctns downloaded your project and it's running on VP20 B326. I have it in loop playback. When I started Vegas, memory used was 904MB. With your project playing in Loop, (8th time), memory usage dropped to 877MB. My system spec is in the signature.

john_dennis wrote on 3/11/2023, 11:22 AM

"I'm surprised to see only Intel video card considering your high-RAM and CPU stats! What is your video acceleration set to in Vegas?"

The work that I'm doing at the moment could be done without a nuclear reactor.

john_dennis wrote on 3/11/2023, 11:32 AM

"If an event is shifted off-frame, did it take a... quantize leap?"

I've had strange things happen with events not landing on frame boundaries with old GPUs drivers and Vegas versions.

Todd-A0 wrote on 3/11/2023, 3:01 PM

I didn't see memory leakage with the test project as presented I tried looped playback and encoding. Also tried with GPU decoder on and encoding Nvenc. (Vp20b326)