Vegas 15 not responding, Friday the 13th

bitman wrote on 4/14/2018, 5:38 AM

I wanted to share my experience of yesterday, which was by chance Friday the 13th, maybe it had something to do with it, but here it goes: yesterday I spend more than 5 hours trying to find a fix for a very reproducible crash (not responding, hang) of Vegas 15 (build 321), until I was frustrated and went to bed. The hang occurred with only one xavc clip on the timeline from a Sony RX10ii(HD 1080/50p), replaying in a loop, sometimes with speed envelope added and sometimes additionally with some insect eye plugin fro Hitfim. Reproducible each time, and I had to stop the program. I tried to isolate the issue and used all the tricks available, one at the time, disable gpu, s04... disable/enable, dynamic mem 0, 200, and larger, nothing helped.

Next day I wanted to further investigate, and guess what, problem gone. I cannot reproduce anymore. The only difference (and maybe decisive factor in my book for this issue), is that the PC has been shut down when I went to bed. I did not reboot my PC during my investigation yesterday (partly because I wanted to hunt down a fix for a reproducible issue, sometimes these things go away after a reboot).

So my question for the developers (if they may read this), is it best to reboot your PC after a Vegas hang or crash due to maybe some corrupt Vegas data cash leftover in memory or disc? With other words, is Vegas start different when starting the first time after a reboot, versus a Vegas start after a close, or a Vegas start after a hang or crash?

Comments

fr0sty wrote on 4/14/2018, 11:01 PM

I'm not sure if it's related, but I do know that sometimes when Vegas crashes, copies of it will remain open in memory, running in the background, and eventually it will prevent you from opening the program anymore. So, in that case, I would recommend a clean reboot after a crash, when you are trying to reproduce it, so that you rule out it being from a crashed copy of vegas or other stuff in the background causing the problem.

Kinvermark wrote on 4/14/2018, 11:24 PM

IMHO, Absolutely. Always reboot after a "bad" exit from the program or you are more than likely to have further problems.

Oddly, I had my first really difficult time with Vegas 14 YESTERDAY, AS WELL. Project with a lot of hours in it would crash Vegas on the splash screen. Vegas 15 (trial version) did the same. Spent couple hours trying to get it to go with no success and was starting to panic. Finally wised up and opened up a test project and methodically tried applying effects until I found the problem plug-in. Re-installed the plug-in and all is well again. No idea why that plug-in stopped working on Friday the 13th though :)

ritsmer wrote on 4/15/2018, 5:55 AM

I have had a year where Vegas 14 build 211 ++ and later all the Vegas 15 builds made a "Vegas stopped working".

Just like @bitman I have user a lot of time to try to find out what caused the crash - and at last I found out that even an empty instance of Vegas (no project loaded - not even added a track on the TL) could crash every 5-10 minutes.

It was so strange that sometimes an instance of Vegas would run for many hours while a second Vegas instance (empty) would crash all by itself after some minutes.

As to OP's question: I have seen hundreds of crashes within the last year in Vegas 14 and Vegas 15. Sometimes I have booted the machine - and sometimes not - but as far as I could see booting or not did not give any difference as to when the next crash came.

After installing an older driver for my RX480 card I have not seen a single crash for some days now. Please see this thread about it: https://www.vegascreativesoftware.info/us/forum/vegas-pro-15-has-stopped-working-constant-crashing--111034/