Closing bug Vegas (build 252)

Kit-As-Was wrote on 5/22/2017, 5:58 PM

On Closing Vegas 14 hangs in the memory for approaching a minute. Worse if I have Vegasaur 3.1 installed Vegas 14 crashes on exit and I get not one but two error alerts (nothing useful just Vegas has stopped working). Has anyone else had problems with Vegas not closing down gracefully. Is there a cure. Thanks.

Comments

NickHope wrote on 5/22/2017, 10:38 PM

I don't get the "hangs in memory" issue but the "Vegas Pro has stopped working" error has been around for years. An SCS developer even spent 4 months working on it. It's better for me in VP14 but I still get it quite often but only when I've been doing stuff with 3rd party plugins.

Martin L wrote on 5/30/2017, 3:55 AM

I also get that sometimes but not always. Something I always get is that Vegas Pro 14 (and 13 too at that time) doesn't open completely at once, ever. It's a minor and strange little problem. When I click to start Vegas, Vegas startup window opens and then it stops right there. It doesn't crash, but nothing happens. I have tried waiting for hours with no further progress in the opening process. But as soon as I click anywhere outside the Vegas window the process immediately continues and in a few seconds it is all done. Funny little glitch.

JJKizak wrote on 5/30/2017, 7:09 AM

I also continually get the Vegas 14 "dump my router" during startup the first time but not the second time as it tries to access the internet. It also happens during upgrades but I am living with it.

JJK

RedRob-CandlelightProdctns wrote on 5/30/2017, 9:11 PM

I've lately had render issues which I am unscientifically associating with Vegasaur's "render assistant".. disabling it then rebooting and starting up again seem to fix the problem. That said, I don't want to slam Vegasaur which I recently purchased and am daily thankful to have it!

 

Vegas 21.300

My PC (for finishing):

Cyperpower PC Intel Core i7-7700K CPU @ 4.2GHz, 64GB mem @ 2133MHz RAM, AMD Radeon RX470 (4GB dedicated) with driver recommended by Vegas Updater (reports as 30.0.15021.11005 dated 4/28/22), and Intel HD Graphics 630 driver version 31.0.101.2112 dated 7/21/22 w/16GB shared memory. Windows 10 Pro 64bit version 10.0.19045 Build 19045.

My main editing laptop:

Dell G15 Special Edition 5521, Bios 1.12 9/13/22, Windows 11 22H2 (10.0.22621)

12th Gen Intel Core i7-12700H (14 cores, 20 logical processors), 32 GB DDR5 4800MHz RAM, Intel Iris Xe Graphics, NVIDIA GeForce RTX 3070 Ti Laptop GPU w/8GB GDDR6 RAM, Realtek Audio

 

 

Kit-As-Was wrote on 5/30/2017, 10:28 PM

I've not had any problems with Vegasaur while Vegas is running and I find it too useful to disable but this closing bug is getting increasingly annoying. UltimateS doesn't cause this problem. I feel the error is caused by Vegas rather than Vegasaur though - Vegas should not be hanging around in memory so long after it is closed. Does anyone have a set up where Vegas closes quickly on exit? Just wondering what causes the problem.