Rendering Issue - "The system is low on memory" in Vegas 21

T-Co wrote on 1/14/2024, 5:05 AM

I have a roughly 90-minute render I am trying to do, but I am consistently getting a "The system is low on memory" error message at points in the render. I will put my specs in the images below, but the brief is:
Windows 10
Vegas 21.0
i5-9400 CPU
NVIDIA T600 GPU
24 GB RAM
1080p Render

I first tried to get through rendering the entire thing, but it would fail with that message at about 16-17 minutes in. The preview screen then went red and I would need to restart Vegas, sometimes it would crash if I tried to Play.
I then tried putting the .veg file into another project and rendering with that instead (which has worked in some cases for me in the past), but it still failed.
I then resorted to rendering 10-minute sections, but it would also fail with the same message (at different places than the full 90-minute render, but again similar, but not the same places within those sections). It's made it to between 7.5-9.5 minute sections so far. It got through one 8-ish minute section and one 10-minute section without it failing (although with the larger renders it had made it to the roughly 16 minutes max consistently from the project beginning).
I tried to isolate as many causes and retry with settings changes as much as possible, but I need to finish the project, so I've just been rendering out as long as I can, then finding where it failed and starting another section to render. I'm hoping that I can stitch them together without it failing in another project.

I tried:
Running in the Compatibility mode for Windows 7
Turning off GPU acceleration in Video Preferences
Reducing Render Threads to 5
Turning off So4 options in Internal
Turning off GPU options in Internal
changing the Dynamic RAM preview to 0/50%/etc
Using RamMap to empty working sets of Memory during the render, keeping the "Memory usage" in the render dialog box below 4 GB
I think a few other things, I've lost track a bit

I am fairly sure that the issue is not actually a RAM issue, as I see no reason to believe that from the task manager, etc. The image with the task manager shows no change really when the render failed. The failure happened maybe 15ish seconds before, as shown in the GPU utilization in the other box in that image (the dip at about 3/4 through the graph).

A few notes:
Preview screen goes red after render crashes
    this also sometimes happens randomly while editing, Vegas must be restarted for it to work again
    Audio still plays sometimes with this red screen, sometimes it crashes the program

Nothing seems to be consistent with the places that it is failing, although they usually fail roughly in a similar place

After getting through a successful render, I tried the next section, and it failed much sooner, leaving me with a 40-second output file (this is the time I took the image attached of the error dialog box).

I did almost the same video for the same event last year, and that time I had no trouble rendering the entire 90-ish minutes. That was done on Vegas 18. The only real difference is the use of Adjustment Tracks/Events in this one. They made the process of editing much easier (and were a large part of the reason I wanted to update), but if they're the reason for these failed renders, that is not ideal. I did this edit with them pretty integral to the process, so I really didn't want to redo it or render without them, but this thread seems to be about a similar issue and seems to suggest they may be the culprit:
https://www.vegascreativesoftware.info/us/forum/vegas-21-build-187-post-render-error-the-system-is-low-on-memory--143455/

If it is indeed the Adjustment Media that is the problem, I would really like it if they are fixed ASAP... They're quite helpful for the workflow, but they are far less useful if they crash the render.

Any help/info would be appreciated. I'll likely be able to get this project done with these sections, but for future reference, I'd really prefer to not go through this. Thanks.

Comments

fr0sty wrote on 1/14/2024, 7:12 AM

Red screen indicates a GPU error.

You're probably running out of VRAM, that T600 doesn't really have much to work with. You really want something more powerful than that for rendering video, especially if you're using effects in the video project that consume some of that VRAM.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

T-Co wrote on 1/14/2024, 2:37 PM

True, but again, seemingly with GPU turned off for rendering the problem persisted, as in that other thread linked, in which the user seemed to have higher-end hardware. I was able to render the sections together in another .veg file without any trouble. I am leaning towards it being something to do with the Adjustment Events used throughout the projects, as again, I did virtually the same project last year with no rendering issues whatsoever before I had Vegas 21 (Adjustment tracks/events being the only difference in the project).

Now that the project is finished rendering as I had to do it, I may try to do a render without the Adjustment events to see if it works when I get some time to do so to see if that works. I will update this thread with the results.

RogerS wrote on 1/14/2024, 5:33 PM

Hopefully the adjustment events can be fixed in a future update as a few people had ram issues with it.

If you could make a short dummy project available with media that triggers this memory issue (just a problem section?) that could help if we can replicate it. Of course that's more work for you so understood if you can't.

T-Co wrote on 1/15/2024, 5:40 PM

So I muted all the tracks with Adjustment events and tried a render of the entire project, and it got through the entire 93 minutes without failing. So it would certainly appear that the Adjustment events were the cause. I did have them on tracks that were Compositing parents of children below them, which I don't often do and could possibly be part of it, but I have done that from time to time before and not had issues, so I would bet it's just the Adjustment events themselves.

I will try to make a dummy project when I get a bit of time if it can help. Thanks!

T-Co wrote on 2/1/2024, 9:18 AM

Quick update - I made a project with a "Test Pattern" generated media for 15 minutes and 3 adjustment media with 1 random effect on each (gaussian blur, brightness and contrast, pixelate) above it and attempted a render of the same settings I used before. It failed at 7:40, though I didn't get the red screen in the preview, it just crashed and I sent a crash report as prompted.

I would attach the file, but it appears I can't attach .veg in this forum post, and it can be easily recreated elsewhere if necessary. Hopefully this helps a bit!

RogerS wrote on 2/1/2024, 9:21 AM

If you could upload it to a free space like Google Drive that could be useful for quick tests.

Glad you were able to send in a report though!

RogerS wrote on 2/1/2024, 9:34 PM

Thanks, I was able to crash it at the 46% mark and sent an error report linking to this thread.

   Fault Address:       0x00007FF78BF7FAB0
   Fault Offset:        0x00000000005CFAB0

Reyfox wrote on 2/6/2024, 8:54 AM

Failed to render here too using AMD VCE. Failed at the 46% mark also. @RogerS I get the same fault address as you do.

@VEGASDerek?

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: Pro 23.Q3

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

RogerS wrote on 2/6/2024, 9:09 AM

Thanks very much for testing. I also get the red screen if I just let it play back for a few minutes.

Reyfox wrote on 2/6/2024, 9:21 AM

I am at the 5min mark and no red screen yet.

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: Pro 23.Q3

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

RogerS wrote on 2/6/2024, 9:43 AM

I looped it and by the time I came back to my computer it had turned red.

Former user wrote on 2/6/2024, 9:46 AM

Tried that project, crash at 45%.

Reyfox wrote on 2/6/2024, 10:15 AM

@RogerS, I let it play through with "loop" on, and when it looped back, it stopped playback at frame 1017, and yes, RED!!

Newbie😁

Vegas Pro 22 (VP18-21 also installed)

Win 11 Pro always updated

AMD Ryzen 9 5950X 16 cores / 32 threads

32GB DDR4 3200

Sapphire RX6700XT 12GB Driver: Pro 23.Q3

Gigabyte X570 Elite Motherboard

Panasonic G9, G7, FZ300

tonytroxes wrote on 2/25/2024, 12:06 PM

Sure! Here's a link: https://drive.google.com/file/d/1MZj5IdCiZzRD0P-J2XANw6OLJXI8Y6x6/view?usp=drive_link

I am also having this issue with my own projects... tested this one just in case and it crashed at the 47% mark 5 times in a row.

Only way to render is without the Adjustment events, its like throwing a 🎲 /_ \

T-Co wrote on 1/10/2025, 2:45 AM

Any update on this issue for versions since then? I just had a similar project over 60 minutes come up in which I used adjustment events as I did in the file I made this thread for, and I've had the same problem (and did the same work-around where I rendered 7 minute chunks, then rendered those together). I'm still on Vegas 21 with all the same hardware, I'm just wondering if this problem is addressed or fixed in any updates or if anybody has had any luck. I don't see any updates to 21 available for me, but maybe in 22?

andyrpsmith wrote on 1/10/2025, 4:14 AM

Giving it a go with V22, on play loop at moment. Passed 1st loop. will try a render after a few play loops.

andyrpsmith wrote on 1/10/2025, 5:23 AM

All good, no crashes with 40 min loop and rendered to MP4 file using Magix AVC. Looks like V22 has no issues with the Veg at least with my hardware.

RogerS wrote on 1/10/2025, 5:41 AM

For me the adjustment event memory leak was also fixed with 22 and haven't seen it since.

T-Co wrote on 1/13/2025, 3:23 PM

That's good news, thanks for checking on that! I'm pretty sure I had updated 21 since I had this issue, but it apparently didn't cover it. Glad to know it was addressed in 22, I may have to upgrade.