Rendering hangs up with a memory leak - Vegas 18 Pro

ngjb wrote on 12/28/2020, 2:34 PM

VEGAS Version & Build

Vegas 18 Pro build 373 - Problem also occurs in previous Version 18 builds

This problem did not occur with Vegas Pro 14.

Windows Edition & Version

Windows 10 Home

Version 1909

OS Build 18363.1256

AMD FX-8120 8 Core Processor

16GB RAM

AMD Radeon R9 380 GPU 4GB VRAM

The problem also occurs on a Acer Nitro 7 Gamer Laptop (Vegas 18 Pro Build 373, Windows 10 Home, Intel Core i7-9750H Six-Core, NVIDIA GeForce GTX 1650, 16GB RAM)

Camera/App that created your footage

Panasonic Lumix G9

MOV (2160,30P) 422/10 Bit/LongGOP/150Mbps

MP4 (2160, 30P) 420/8 Bit/LongGOP/100 Mbps

MP4 (2160, 60P 420/8 Bit/LongGOP/150 Mbps

Your Delivery Destination

YouTube

Exact symptoms of your problem

This problem is fairly easy to reproduce on both my AMD based desktop and Intel based laptop. A video is attached to illustrate the problem. As shown in the video, four clips are placed on the timeline and some minor color correction is applied (the color correction does not cause the problem) and the video is rendered without any issues using MAGIX AAC/AVC MP4 and AMD VCE. In the video, I started the task monitor to illustrate that the memory utilization is stable throughout the rendering and CPU utilization is between 50-68% during the rendering. I then added four simple titles using Vegas Titles & Text. I then rendered the video using the same settings as before. You can observe in the attached video that when title overlays are used, the memory utilization increases when titles are being rendered and continues to increase until the rendering hangs up. The CPU utilization drops also when the rendering hangs. If I only used one or two titles, the rendering will complete. If I used 1080P MP4 media, the rendering will complete without issues. If I used a solid color as the background media to the titles, the rendering will complete without issues. Using Vegas Titles & Text on any 4K media (10 bit, 8 bit, 30P or 60P) causes rendering to hang. It also occurs on my Intel based laptop with an NVDIA GPU but it fails during the first title overlay with the same symptoms. I can get it to fail without using GPU rendering. This is a definitely a bug in Vegas Pro 18. I did not have this issue with Vegas 14 Pro. The video should provide enough information for Magix software personnel to investigate.

Update: I repeated this test using 4K30P media from a Yi 4K action camera and was able to render with titles without any issues. So the problem appears to be limited to media generated from Panasonic Lumix G9, G7, and GH5 cameras in the formats mentioned above. If I render (with titles) the Panasonic 4K media mentioned above as a 1080/30P output, it works without any issues. It consistently fails at 2160P output. The symptoms are always the same with memory increasing as it renders with each title and then when rendering hangs up, the CPU load drops below 5% which is a good indications that the Vegas task is in a deadlock state.

Back to post

Comments

RogerS wrote on 12/29/2020, 11:15 PM

Our settings are pretty similar.

ngjb wrote on 12/29/2020, 11:26 PM

@RogerS Good to hear that you are getting results that are consistent with what I am seeing. I tried other codecs also but got the same results. The issue so far limited to the new Titles & Text function which I hope they fix someday. I want stay with Panasonic and 10 bit color. Panasonic makes some great 4K cameras at affordable prices.

RogerS wrote on 12/29/2020, 11:40 PM

One thing I noticed is that I don't have a Intel QSV render setting under Magix AVC so I can't test that, just Mainconcept and NVENC. I don't know why it's gone or how I can get it back.

Intel QSV does appear as a render option under HEVC. I did two renders with titles and text. The first was in 8-bit project mode. Vegas ram usage was steady at 4.2GB. System usage steady through the render at just 12.7GB. CPU is around 100% and Intel GPU just 3% utilization or so. The render completed in 5 min without error.

The second was in 32 bit mode. Vegas ram usage was 4.08GB. However system ram usage continued to climb through the render. It failed with total memory use around 20GB even though Vegas reported just 4.07GB used.

So my conclusion is that 32-bit video mode and titles and text don't get along whether in CPU, QSV or NVENC mode.

LongIslander wrote on 12/30/2020, 12:17 AM

I had no issues rendering a 8bit or 32bit 4k file.

Trying turning off Hardware Decoder and Set Dynamic Ram to 0.

Additionally when rendering use a "mainconcept" encoder option" which is a 100% cpu software encode.

Also. Increase your pagefile to the maximum size your drive supports. This may help.

RogerS wrote on 12/30/2020, 3:56 AM

Thanks for more workaround ideas to better isolate this bug, which is my only goal. I don't actually care if it renders.

1. Tried with dynamic ram preview = 0 (was 200). Did another UHD Mainconcept render (variable bit rate with default values). Vegas memory flat at 4.2GB but in use system memory continues to increase until about 19GB used and the render fails at ~67%. Closed Vegas and system usage dropped to 8.2GB.

2. This type of file doesn't work with hardware decoding. However for the sake of testing disabled it (was Auto/Intel) and did a UHD Mainconcept MagixAVC render again.
Vegas ram usage at 4.09GB. System use continually climbs. Took screenshot at ~67% and Vegas crashed...

3. Where is the pagefile setting? Normally Windows just allocates it? I'm somewhat space limited on SSD system drives. Really though, I can do a 4K render of such a simple project in 8-bit mode with no issue.

I tried to switch from 32-bit video to 32-bit full range mode but couldn't get the picture to show up in preview anymore. I deleted and readded it from the media bit and then assigned color space Rec 709.
Did a NVENC render with decoding back on (still not doing anything) and dynamic ram preview=0. Vegas is at 4.61GB memory use. System use is flat around 14.2. It rendered without issue.

j-v wrote on 12/30/2020, 5:03 AM

@RogerS
As a side step

One thing I noticed is that I don't have a Intel QSV render setting under Magix AVC so I can't test that, just Mainconcept and NVENC. I don't know why it's gone or how I can get it back.

I saw the same on my old laptop, where I had to dive very deep in the BIOS to allow the option to be visible. After a restart I saw it mentioned in device manager / display adapters. Therefore it was not available but it was already before the change available in Magix HEVC

RogerS wrote on 12/30/2020, 5:19 AM

@RogerS
As a side step

One thing I noticed is that I don't have a Intel QSV render setting under Magix AVC so I can't test that, just Mainconcept and NVENC. I don't know why it's gone or how I can get it back.

I saw the same on my old laptop, where I had to dive very deep in the BIOS to allow the option to be visible. After a restart I saw it mentioned in device manager / display adapters. Therefore it was not available but it was already before the change available in Magix HEVC

Thanks for entertaining this side conversation. I do have Intel HD Graphics 630 visible in Device Manager and the Intel software assistant keeps my drivers updated. Do you think there is anything more I can do in the system bios? Seems odd that it appears under HEVC but not AVC.

Edit: apparently this is a symptom of moving to DCH drivers. Vegas needs to be updated link

After checking in with our devs it was determined that the affected applications need to be rebuild using an updated Intel® Media SDK.

j-v wrote on 12/30/2020, 5:49 AM

No idea what the reason is, but maybe it has to do with those DHC drivers, because on my new laptop I see the same again in VP17 , but not anymore in VP18. But because it is available in the latest I don't care anymore.

RogerS wrote on 12/30/2020, 6:03 AM

No idea what the reason is, but maybe it has to do with those DHC drivers, because on my new laptop I see the same again in VP17 , but not anymore in VP18. But because it is available in the latest I don't care anymore.

That is interesting it works for you in 18. I don't see Intel QSV options for MagixAVC in either 17 or 18. Oh well, I have no plans to ever use QSV anyway.

ngjb wrote on 12/30/2020, 2:49 PM

My preview RAM was already set to zero. I set the File I/O hardware decoder to OFF and saw no difference. It still causes a memory leak with Titles & Text. When I have some more time I will load Vegas with the Visual studio debugger to get an idea of what exactly is going on. I need to get out of the house and get some fresh air. My wife is getting cabin fever.

RogerS wrote on 12/30/2020, 8:20 PM

@VEGASDerek When you get back, could you take a look at this issue with the new titler and 32-bit video levels mode with 10-bit footage? It appears to trigger a memory leak that crashes renders.