Prior to this build, VP behaved itself and "Left The Building". But now, according to Task Manager it's remaining in memory, like a bad date or bad smell that . . .. far too graphic. OK, Brethren and Sistren - what gives?
Yup, still there, well after Closing Time at Pub MAGIX.
@Howard-Vigorita Interesting, I observed the TCP connections for Vegas 16 on windows 10: you can do this via the taskmanager, then tab performance, next open resource monitor (bottom left of window) , next select network.
After opening Vegas, you see a few connections (license check?, upgrade offers?), but then after a brief period all is cleaned up.
@bitman yes, Win10 Resource Monitor... also listed in Win admin tools if you want to pin it. Have Vegas on 2 Win10 systems and they're clean as a whistle. I expect they'll fix this soon because from the server side it probably looks a dos attack of the VP zombies.
I'm still getting the memory-resident problem with build 424. In my case if I exit Vegas Pro 16, forget to kill the memory-resident process, and try to restart Vegas later, it will hang on "Initializing UI". Killing the process allows Vegas Pro 16 to load again, but it's a pain to have to keep doing that.
My OS is Windows 7 Home Premium, graphics card NVIDIA GeForce GTX 645
I see from earlier posts that re-installing Windows 7 or upgrading from Windows 7 to Windows 10 fixed the problem. I certainly don't want to upgrade to Windows 10, and I'd like to avoid re-installing Windows 7 if I can. Is any work being done on this problem in build 424 these days? Will I have to upgrade to Vegas Pro 17 to fix it?
I have other problems with build 424, but those are described in a different thread, "Audio rendering fails in Vegas Pro 16 build 424"
@AlanMintaka windows 7 is a dead end. Support for it in both SW and HW is already fading and no more security updates, well hackers will love it when you stay with win7.Microsoft "mainstream support" for Windows 7 ended in January of 2015, and the end of “extended support” is January 14th, 2020.
So, do you know why Vegas Pro 16 424 stays resident in memory when the program is exited?
...a tool which overrides the issue is to be found -> here.
UPDATE: wwag has just uploaded a new version of killvegas.exe to DropBox. It fixes the unhandled exception error I reported in my previous post.
Many thanks to Marco and wwag for posting info about the app.
BUT: I've now upgraded from VP16.424 to VP17, and VP17 has the same problem - the program stays in memory after being exited. If it's restarted while the memory-resident process is still running, it hangs on "Initializing UI...."
The good news is that wwag's killvegas.exe program kills Vegas Pro 17 processes too. It's a handy workaround, though not a fix for the memory-resident problem.
Magix, are you working on this? Anyone else find a way to keep this from happening in VP16.424 and VP17?
Just upgraded to Vegas Pro 17 on my latest-OS-version Win10 system, and I notice that Vegas still leaves a background process running when it exits. The background process causes problems with other apps such as Adobe Photoshop, and DVD Architect and perhaps others. Part of my Vegas "Standard Practice" is to go into Task Manager after exiting Vegas Pro, and ending the background process there.
Just installed a new Dell laptop yesterday with Win10 1903 and noticed both VP16 and VP17 leave a zombie background process running after exit. Looks like it sits there for about a minute before some other process, perhaps the video driver, terminates it. But if I restart Vegas before it gets killed, it stays on consuming a couple gigs of ram.
Same a Grazie, but I run VP17 on a solid Win 10 Pro machine with 32GB RAM... My VP16 v424 works and closes fine. This new install of VP17 developes a new (hanging on) process in TM for each instance of VP17 started up....dependably. (4 starts... 4 instances in TM). After reading this entire 4 page thread... it seems like a good practice (if not using Waag's kind offering), is to do as Ernie-Tamminga says, "Part of my Vegas "Standard Practice" is to go into Task Manager after exiting Vegas Pro, and ending the background process there".
Sure hope there's a fix by Vegas, soon. Thanks for ALL the support Forum people!
The last time i saw this kind of issue, was with 3DSMax. And the cause was not the software but the VRay plugin, which did not close properly and prevent to kill 3DSmax process. Maybe the same with Vegas. Maybe investigate plugins instead of main program is the way to find solution.
(edit updated) Problem was there with Intel onboard Video and prior to update 1. I changed to NVidea GPU and updated to (VP17) Update 1, and problem is gone. VP service does not hang around after closing now.
wrote on 9/27/2019, 11:35 PM
Here, I fixed this bug and many others that happened by changing the native language of Vegas which is English to the language of my operating system which is Portuguese.
Perhaps many bugs that occur in Vegas are a language problem. But I'm not a programmer and I don't have the technical knowledge to say that.
I hope this information can help other users as well as developers in solving this and other bugs that exist in Vegas.