Hang/crash Bug in Vegas 12/13 with Titles & Text

NormanPCN wrote on 4/18/2014, 6:12 PM

I reported a bug to SCS on 2/8/2014. They have not yet responded. I provided an example VEG file to reproduce the problem.

Hopefully someone here can reproduce this report.

I had experienced this bug in a couple of projects. One a year ago and the other a few months ago. Initially, Vegas just hung and you had to forcibly close Vegas via the task manager. Then at some newer build of Vegas they added code to detect certain hangs and the crash report dialog then came up. I submitted reports via that with detailed comments, and opened my old year old project and ran that to get the hang/crash and submitted reports via that specific crash/hang as well.

I then decided to create a tiny sample project with the problem Titles and Text events and nothing else. Who knows what detailed info the problem report dialog gives Sony. A sample VEG is as good as it gets.

My workaround for this was to use selective prerender around the text events or turn GPU OFF.

Here is the text of my report to Sony and my sample VEG file (5KB).
https://dl.dropboxusercontent.com/u/51868591/Animated%20Text.zip

In two projects I have gotten numerous crashes on playback with animated titles and text. The error report dialog comes up and I have submitted the reports numerous times.

I have created a small Vegas project with these two text events to give you something which should reproduce the problem for you in house. The VEG file is attached. I have not included the video file to keep the file upload small. My video file was 35 seconds of XAVC-S 1080 29.97 video. You should be able to create this yourself.

There are two titles and text events in the project. I have duplicated them a few times each. One event animates by keyframe movement of the Y position. The other is a predefined animation, "jump" to be specific.

The problem does not crash 100%. Just very frequently. My playback settings are typically preview Half. It seems to only crash when GPU is enabled and other GPU effects exist at the same time. I commonly have the Sony curves effect. If you have to loop to get a crash/hang then make sure your preview ram preference is not so large such that Vegas caches the playback.

My machine is i7 4770k CPU, 16GB ram, Windows 7 64-bit
AMD 7950 GPU, driver 13.12 (current release)

I forgot something in my original report so I added the following.

My apologies. I uploaded another VEG file. The Text animation using "jump' needed to have a video bus motion blur as that is what my original project had. This project has a 15% motion blur, gaussian asymmetric, applied to this text event. Motion blur is only applied to this text event.

It will crash, with Vegas error notification dialog, without the motion blur. It just crashes less often.

I am trying to reproduce what was in my other project(s) as precisely as possible in this small example.

Comments

NormanPCN wrote on 4/21/2014, 5:14 PM

I added another example file upload with VEG and this time with a short looped sample video clip. With this you do not need to supply your own clip to test if you can reproduce this bug.

Since this is a GPU issue, please state your video card brand. AMD, Nvidia, Intel.
Setting the preview RAM to the default 200 might be best for this test. I typically run with 1024.

19MB file.
https://dl.dropboxusercontent.com/u/51868591/Animated%20Text%20(2).zip

OldSmoke wrote on 4/21/2014, 6:01 PM

No issue here but there is no video bus motion blur in the project.

Edit:
Found the motion blur envelop! It was hidden all the way on the bottom. No issue here; I had it looping for 5min.

NormanPCN wrote on 4/21/2014, 7:00 PM

Thanks OldSmoke for trying my example project. Appreciate it.

We are only two data points but right now it is AMD (me) a no go and Nvidia (you) okay.

I have to ask, but since you looped, was your preview RAM set small enough to stop caching. I made the project 35 seconds to avoid that caching but some have some massive preview RAM settings.

OldSmoke wrote on 4/21/2014, 7:06 PM

My preview ram has always been at the default 200, that is the best on my system. Would be interesting to see the test on a AMD/ATI 6970 or older, I believe it has to do with yours being a newer card.

set wrote on 4/21/2014, 7:23 PM

Tested here in my Spec#1.
Dynamic Ram was set from 200 to 0 (zero) due to previous playback of my recent edited clip was ended in error too (Total freeze Not Responding crash, unable to send report). Doing this fix the problem (similar as I tried VP12 first time)

Playback looping, and try set to Best (Full), didn't make it crash.
Render to Mainconcept MP4 done in 3m5s without any issues.

NormanPCN wrote on 4/21/2014, 7:54 PM

Would be interesting to see the test on a AMD/ATI 6970 or older

I have an old 5850 card. I could replace the 7950 and try it. I do not have to change the drivers.

I cannot remember if I was bitten by this bug before I got the 7950 or not. It has been over a year.

@set> Dynamic Ram was set from 200 to 0 (zero)

Thanks for running the test.

In the past for me setting preview RAM to zero, often made things work. I had another hang in a slideshow project and preview ram 0, or GPU off stopped the hangs.

The default 200 is probably the best thing to try.

NormanPCN wrote on 4/21/2014, 8:14 PM

I am sorry guys. My bad. My second upload with the sample video clip had the video track effects turned off. If you already downloaded the file then just enable the track effects. I replaced the upload file.

The bug typically only shows when you have animated T&T, and some other GPU effects all going at the same time. T&T is also GPU accelerated. That happened in VP12.

OldSmoke wrote on 4/21/2014, 8:54 PM

I noticed that and did switch all on when I did my test.

set wrote on 4/21/2014, 9:28 PM

update:

- Turning ON all effects, while keep Dynamic RAM to 0 (zero) : pass

- Change Dynamic Ram to 200 again (play Best Full) : crash instantly in the middle of 2nd Effect, stopped at 00:00:10.17 (as motion blur active on that section)

Extra Information
File: C:\Users\Set 2\AppData\Local\Sony\Vegas Pro\13.0\dx_video_grovel_x64.log
File: C:\Users\Set 2\AppData\Local\Sony\Vegas Pro\13.0\svfx_video_grovel_x64.log
File: C:\Users\Set 2\AppData\Local\Sony\Vegas Pro\13.0\ocio_x64.log
File: C:\Users\Set 2\AppData\Local\Sony\Vegas Pro\13.0\dx_grovel_x64.log
File: C:\Users\Set 2\AppData\Local\Sony\Vegas Pro\13.0\gpu_video_x64.log
File: E:\TEST\NormanPCN Titles-Text problem\Animated Text.veg

Problem Description
Application Name: Vegas Pro
Application Version: Version 13.0 (Build 290) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Windows\system32\amdocl64.dll
Fault Address: 0x000007FED22C3862
Fault Offset: 0x0000000000623862

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 13.0\vegas130.exe
Process Version: Version 13.0 (Build 290) 64-bit
Process Description: Vegas Pro
Process Image Date: 2014-04-10 (Thu Apr 10) 03:27:08

Got the same thing to VP12, although it need more time to crash. I caught it after 5 times looping playback.

Extra Information
File: C:\Users\Set 2\AppData\Local\Sony\Vegas Pro\12.0\dx_video_grovel_x64.log
File: C:\Users\Set 2\AppData\Local\Sony\Vegas Pro\12.0\svfx_video_grovel_x64.log
File: C:\Users\Set 2\AppData\Local\Sony\Vegas Pro\12.0\ocio_x64.log
File: C:\Users\Set 2\AppData\Local\Sony\Vegas Pro\12.0\dx_grovel_x64.log
File: C:\Users\Set 2\AppData\Local\Sony\Vegas Pro\12.0\gpu_video_x64.log
File: E:\TEST\NormanPCN Titles-Text problem\Animated Text.veg
File: D:\Master-ITB_24bit_48kHz.wav(*)

Problem Description
Application Name: Vegas Pro
Application Version: Version 12.0 (Build 770) 64-bit
Problem: Unmanaged Exception (0xc0000005)
Fault Module: C:\Windows\system32\amdocl64.dll
Fault Address: 0x000007FED5FA3862
Fault Offset: 0x0000000000623862

Fault Process Details
Process Path: C:\Program Files\Sony\Vegas Pro 12.0\vegas120.exe
Process Version: Version 12.0 (Build 770) 64-bit
Process Description: Vegas Pro
Process Image Date: 2013-11-20 (Wed Nov 20) 09:45:00

(*)Why this one is noted here? <- It is a wave RF64 issue I had sometimes ago.

monoparadox wrote on 4/21/2014, 10:23 PM

No error running it on my laptop Intel HD4000/Vegas 13, although performance is limited. I'll give it a go on my desktop with Radeon 7870 tomorrow.

tom

monoparadox wrote on 4/22/2014, 9:41 AM

Norman,

No crash with Radeon 7870/driver 13.12 on either Vegas 12 or 13.

update: did a little more testing: no problem in Preview/half. Consistently crashed in Best/full. Preview ram is set at 200.

tom

NormanPCN wrote on 4/23/2014, 10:34 AM

Thanks guys for running the test.

Since this problem appears to be a timing race condition, changing things like the preview size, preview ram zero, CPU speed, can make the problem show or hide itself to a certain degree. It changes the precise timing of a sequence of internal events.

The text event with the "jump" animation originated in a 30p project with 60p source, and then eventually changed to a 60p project. In this example test project, I get the problem primarily with the bounce text event.

So far we have.
2 AMD, both show the bug.
1 Nvidia, seems fine
1 Intel, seems fine

Stark Source wrote on 5/9/2014, 1:41 PM

I'm on an AMD CPU (AMD FX-8350 4.0GHz 8-Core), and my GPU is (MSI GeForce GTX 780 3GB TWIN FROZR).

I'm getting this crash on my video previews and renders when using Title and Texts.

Any advice on what to do? The above thread is a little hard for me to make sense of... It's a little frustrating after paying so much money, only to have a basic function crash the program.

ChrisDolan (SCS) wrote on 5/9/2014, 4:01 PM

I reproduced this crash with "Animated Text (2).zip" on my AMD Radeon HD 5800 machine but not my AMD FirePro V8800 machine. Both with VP13 b310.

On the Radeon, the crash occurs on a thread started by the AMD driver and the crash is in the amdocl64.dll library. The AMD driver is trying to release some memory, but it finds that the map of used/unused memory has been mangled (heap corruption). I can't tell what memory AMD is trying to interact with and I can't tell why it failed. The crash occurred after roughly 5 minutes of looping.

My FirePro has been playing the project for about 45 minutes now without a crash. The Radeon is running driver 13.25.28.2 on Win8.1, while the FirePro is running 12.104.2 (catalyst 13.1) on Win7.

---

I realize most of this information is useless to you because (of course) you'd rather see it fixed than just reproduced, but I wanted you to see that we're listening and trying to solve these issues, but they're really hard.

NormanPCN wrote on 5/9/2014, 8:38 PM

I realize most of this information is useless to you because (of course) you'd rather see it fixed than just reproduced, but I wanted you to see that we're listening and trying to solve these issues, but they're really hard.

Thank you Chris. This is an amazing post from you. While the technical details are of no use I do appreciate you trying to reproduce this crash. This is far better than SCS support which is telling me to uninstall a wacom tablet driver. I do not own such a device, never have, or do I have such a driver.

You need my setup. 90% of the time I will get a hang within two loops. I am available for any info which can help. A remote session even.

Ways to increase the crash percentage.
Changing some effects (add/remove) varies the frequency. For example, if I remove the track effects, then it suddenly becomes stable. Maybe you need to add/remove another GPU effect to change the timing to get a better frequency. I am just unlucky to have stumbled across the exact settings for instability with my CPU and GPU and source material.

Try different source video types. If I change the source video type, it varies the crash frequency. My example with XAVC-S on my machine was chosen for super frequent crashes.

NormanPCN wrote on 7/21/2015, 5:32 PM

With the new/current AMD driver 15.7 this GPU hang/crash which I could easily reproduce on my machine configuration now seems to be reliable. Fingers crossed, knock on wood, that there was a real bugfix and not just timing/sync changes and I am getting "lucky" for the time being.

This test. Vegas 13 Build 453. AMD driver 15.7.

With all the GPU problems that get reported and talked about; I thought I would report something that has gotten better.

Whenever I get a new Vegas build or install an updated driver I have ran this test project and always could reproduce the hang/crash, and 80% of the time the Vegas problem dialog comes up and I added comments to the report.

In case anyone ever has this problem, and searches the forum looking for answers, there is a workaround as follows.

Do not use the media generator X/Y position to animate the text but leave the text position static and bounce the text with pan/crop. A side bonus is MUCH better (perfect) playback performance.