@chell Not seeing the issue on my 11900k/5080 64gb win11 23h2 system with either vp22 or vp23 in 2- to 3-hr projects. I had dynamic ram preview set to 10% but dropped it down to 5% about a week ago for a small across the board render speed increase... setting it to zero lengthened my render times. Perhaps it's a media issue? Mine is all 4k low-gop 4:2:0 hevc & avc mp4 & mov video plus 24bit pcm audio.

Perhaps it's a media issue?

Afraid it's not a media issue. I've tried various different file formats, layers of compression, effects, no effects - if my dynamic ram is turned on at all I get a vram memory leak. Tried everything. I'm really careful about my file types to optimize performance.

@Howard-Vigorita

I'm happy to test anything with my 5070 (12GB VRAM) but haven't noticed any issues and never disable dynamic ram preview.

Could you press play on a timeline with a couple of tracks with dynamic ram turned on and keep an eye on your gpu memory to see if it climbs? @RogerS

With a 30min 4K XAVCS project (no music track) and one Video plus associated sound track ,I get the following VRAM usage via 16GB RTX 4080 super

No Play 8GB usage

Playing:

V23:
0% Dyn Ram 9GB usage
5% DRam 14GB
10% DRam 14GB usage

V22:
0% Dyn Ram 9GB usage
5% DRam 14GB
10% DRam 14GB usage

Interesting. Very similar to mine then. If you continue to play the video uninterupted and click into other programs, does anything else begin conking out and failing for you like it does for me?

Thank you for testing it out @andyrpsmith

By design VEGAS consumes most VRAM and hands the memory back when not in focus. It's pre-caching when you play it back for better performance.

@RogerS Yeah, the issue for me though is that its not releasing it. Each time i hit play it eats more, and it doesnt release until i either turn off dynamic ram or close out Vegas. At a certain point everything begins crashing because theres nothing left for other applications/drivers.

It also makes playback much worse because after 5-10 second of playback vegas has eaten almost all of my available vram. :(

no ide what to do bout it

I did a test with a few pieces of AVC media and it uses 9.8/12GB of VRAM once it increases from the idle amount. Dynamic ram preview is at 10% as always.

I didn't see a dropout when just clicking to my browser- is the other program you are using GPU enabled? I have seen the screen go green when clicking over to another program that is.

My guess is that this is a media specific issue or conflict with particular software I don't have (do you have any GPU management software in the background?) Tested with my 5070 12GB.

@RogerS I thought this could have been the case myself so I ended up closing Discord & Opera and the result was exactly the same. Then i closed all of my non vital background processes so it was just Vegas and Task manager and it still happened. Really havent a clue what's causing it. Its completely stable with dyn ram at 0%. My brain is muddled haha.

I tried it again earlier today to see how much it would climb. It got to 14.9/16GB before my mouse started dragging freezing, audio drivers failed and vegas then crashed completely.

If it's not media or Fx or obviously conflicting application-related I think this is beyond what I can help troubleshoot and I'm not seeing widespread reports of such a memory leak- have you filed a support request? They might have an idea of how to figure out the cause.

@RogerS It is strange. Looking at Andys results above, they're very similar to mine - however it really depends if perfomance deteriorates past a certain point for him too. Im very curious to know. I appreciate you taking the time to share your findings!

My results seem the same as Andy's- he has a 16GB GPU, I have a 12 and it uses all but ~2GB or so. There's no degradation here in performance. Happy to test more if you can point me in the right direction and I'll keep an eye out as I use the program!

If I open both V22 and V23 both with media playing, the VRAM seems to be shared 50% each and if I stop one then VRAM is released and taken up by the other. It never uses 100% of VRAM. If both are stopped playing then VRAM is released back to 9GB each. One issue I did notice however and I reported this is that if both V22 and V23 are playing the same project (each with their own Veg file) V23 slows down and plays with reduced frame rates approx 15 - 12 fps from 25fps. V22 seems unaffected and keeps going at 25fps. Also playing clips with Mercalli 6 stabilization V22 runs at full speed while V23 playing the same clip runs at 11-12 fps. It's as if V23 is not using the GPU as much as V22. In all cases I have not found V23 with the new engine any faster than V22. I have a setting in the V23 internal menu set to True for releasing memory. Just had a look it is - Releasing Inactive Image buffer CPU and GPU memory. There is a setting for both. I have not seen any issues with other programs when V23 or V22 is taking high VRAM, and it is released when Vegas is terminated.

I will try running V23 and when it is using 14GB of VRAM I will fire up the game Stalker 2 and see what happens.

OK, V23 on it's own playing and Task Manager reporting VRAM usage of 14GB (includes windows usage) runs at 25fps with no fx applied and 11fps when fx applied. fire up the game and the game runs at over 100fps and reports VRAM usage at 15.9GB (the game typically uses 7GB - inc windows usage). V23 frame rate drops to 10-15fps. when playing game you can hear V23 playing in background. No crashes of V23 or game. Close down V23 and VRAM releases to 7GB which is normal when playing the game. Fire up V22 and when playing same project V22, game and windows VRAM usage is 15.9GB - but V22 is running at the full 25fps no slow down. Also playing game and V22 together no crashes. So again V23 does not play back at full frame rate when other apps are in use, whether this is VRAM related I do not know. In all cases VRAM is released by Vegas when paused or closed.

Here in Vegas Pro 22, I have to close and reopen the program every 30 minutes or so because the VRAM bottleneck consumes RAM until the entire system crashes. I had to add virtual memory to avoid having to restart the computer. It really seems like the buffer isn't releasing the memory when playback stops.

It's not a plugin/LUT issue or anything like that. Here, with a simple 1-minute timeline with no effects or anything, the project starts and memory usage starts at 10GB... playback alone, if I watch/play it about 15-20 times without any effects, it already consumes 12GB of RAM + 32GB of RAM. 😥

I've tried every possible option in Vegas. The only solution is to disable GPU acceleration. However, playback is poor; when I apply any effect, playback becomes impossible. Proxies don't work for me. I work with a weekly project/delivery pipeline of 200 GB of raw files.
The "Enable legacy AVC decoding" option uses 50% of the GPU's VRAM. However, over time, VRAM usage continues to increase, and some issues arise... even when I enable it, playback stutters and the program frequently crashes.
I've also used and tested several media files. They all have the same issue.

I hope this issue will be resolved one day. There's no point in installing 64 GB if Vegas continues to consume all the memory after a while.

Have you turned off dynamic ram completely? If you're on 23, theres a setting to change the settings for releasing inactive image buffer for GPU and CPU to TRUE in the internal settings. Doing this is the only thing that's kept things stable for me. It only takes 2 minutes of playback for Vegas to eat ALL of my vram and crash everything else when I don't have my settings like this.

I'm relieved its not just me experiencing this and I'm not crazy but at the same time frustrated that it's happening at all.

@JulioAZ

@andyrpsmith Does the vram release when you pause playback, or only when you close out Vegas entirely? Does it continue to climb past that point?

@RogerS Is there any chance you could try to replicate the test i ran in the first video? In the video you see it climb until i hit pause and it does not release until i turn of dyn ram. If i were to have hit play again it will have exhausted all of my vram and everything would have crashed again. I suppose im trying to see if its only a few of us that are getting a leak where theres no limit to how much vram it eats VS some people having a hard set limit some how so their system remains stable. Im very curious to know!

So V23 30min project with some FX, grabs 14 GB Vram and keeps it until it is closed. Add in V22 with 14min project and it takes rest of Vram. Initially with both playing they both run slowly 2-14 fps rather than 25fps. Pause either and the Vram stays at 15.5 out of 16GB. Shared ram goes up to 5-8GB (out of 47GB allocated by windows). The only time Vram is released is when either is closed down. V23 is always running slow when sharing Vram while V22 can run at full 25fps. Again no crashes from V22 and V23.

Have you turned off dynamic ram completely? If you're on 23, theres a setting to change the settings for releasing inactive image buffer for GPU and CPU to TRUE in the internal settings. Doing this is the only thing that's kept things stable for me. It only takes 2 minutes of playback for Vegas to eat ALL of my vram and crash everything else when I don't have my settings like this.

I'm relieved its not just me experiencing this and I'm not crazy but at the same time frustrated that it's happening at all.

@JulioAZ

In the last test, I left dynamic allocation at 0%. Nothing changed. Here are the screenshots showing the problems I've been experiencing:
01-Vegas Closed;
02-Vegas Open, Project open but without any video playback. Time: 16:04;
03-I let the video play, starting playback/editing. Time: 16:05
04-Editing: Time: 16:15;
05-Editing: 16:30... RAM bottleneck in the system;
06-I closed Vegas and reopened it.

123456

I do this cycle of closing and reopening Vegas for ALL projects, from the largest to the vertical versions.

What would the "image buffer" option be? I don't know which one in VP22.


Internal has these options. Maybe even a Vegas programmer could advise if anyone can resolve this issue. Like Video RAM Buffer. I'll test some soon, but I don't think we should change much there.

@Reyfox

I'll have to highlight this here to centralize the issue.

All the files I used are 8-bit and not an isolated file type. 4k (30 and 60 FPS) GH5 H.264, G7, Sony's XAVC, Fujifilm's Hevc/H265 files... all show the same RAM consumption evolution.
What really changes is the amount of playback time that accumulates VRAM usage. Something in the decoding process is really not working properly.