Vegas 9d never completely shutsdown?

YesMaestro wrote on 5/6/2010, 6:51 AM
Throughout the day yesterday, I opened and closed Vegas about half a dozen times. Today when I got into the office, my computer was running very slow. I opened Task Manager and saw that there were six Vegas9 process still running even though I had closed them shut them down yesterday. Any reason why they should still be running?

Paul

Edit: I'll add that this has never happened before so I'm just wondering.

Comments

farss wrote on 5/6/2010, 7:35 AM
I've seen this happen with other releases of Vegas, mainly when it had crashed it would still leave the Vegas.exe process running. It certainly pays to check for this with Task Mananger as I'd guess having another identical process running could contribute to further problems.


Bob.
fordie wrote on 5/6/2010, 7:57 AM
Paul,
Ive seen this with 9c all the time and with 9d even without a crash.
Grazie wrote on 5/6/2010, 8:21 AM
ditto . . . and ditto . . .

- g
YesMaestro wrote on 5/6/2010, 8:41 AM
Glad that I'm not the only one. At least I didn't have any crashes. I can see your point Bob in how it can possibly lead to other problems. I'll keep an eye on it in the future.

Paul
douglas_clark wrote on 5/7/2010, 3:34 PM
I've seen the same thing. I exit normally from 9d, but when shutting down the PC later, I see message that shutdown is waiting for vegas to exit. Ie, it's still in memory.

Home-built ASUS PRIME Z270-A, i7-7700K, 32GB; Win 10 Pro x64 (21H2);
- Intel HD Graphics 630 (built-in); no video card; ViewSonic VP3268-4K display via HDMI
- C: Samsung SSD 970 EVO 1TB; + several HDDs
- Røde AI-1 via Røde AI-1 ASIO driver;

Editguy43 wrote on 5/7/2010, 6:23 PM
I have had the "waiting for vegas to exit" a couple of times but not lately I just opened 5 Vegas 9d and 2 Vegas 8c and then closed them all and not one stayed open in the process section, I did not do any work just open and close, I wonder it it happens when you have done some serious stuff like effects, or render? might be worth checking that out.

Paul B
Yoyodyne wrote on 5/7/2010, 8:10 PM
I've seen this too. Weird, sounds like a little bug.
Kevin R wrote on 5/8/2010, 4:46 PM
Vegas actually launches several processes:

vegas90.exe (Vegas Pro)
ErrorReportLauncher.exe (Error Reporting client launcher)
FileIOSurrogate.exe (File I/O Surrogate)
sfvstserver.exe (Sony VST Server)

These should all terminate when Vegas is closed. When rendering fails with an exception I have seen some of these processes be orphaned and left behind--mostly FileIOSurrogate.exe. Sometimes the orphaned process continues to "render" blindly using up CPU resources even after Vegas has crashed and has been terminated.
rmack350 wrote on 8/3/2010, 2:55 PM
I've been noticing that Vegas doesn't shut down over the last few days. I could open Vegas and just have a blank new project loaded and Vegas would still have troubles unloading itself.

I *think* it does eventually close after a very long while so if you've closed Vegas an hour before you turn off your PC you might not notice anything.

Of the processes Kevin R listed I see Vegas90 and ErrorReportLauncher still running. Killing ErrorReport Launcher doesn't result in Vegas90 closing. Killing Vegas90 also closes ErrorReportLauncher.

I'm running 9.0e
willqen wrote on 8/5/2010, 2:57 AM
Lately, often when I close Vegas Pro 9.0e the Error/Reporter stays open wanting to know if it should send a blank error report. I just close it but it is somewhat irritating.

Will
zcheema wrote on 8/5/2010, 2:25 PM
Ditto, Ditto
rmack350 wrote on 8/5/2010, 4:26 PM
For me, taskman says the error reporter is still running (as is Vegas90.exe) but neither of them are on screen. Without Taskman I'd assume that Vegas had closed.

It seems to take about a half hour or so for Vegas to close. I'm thinking it's networking related. Maybe Error Reporter is waiting for a network response...

I should submit this to tech support. (done)

Rob
willqen wrote on 8/7/2010, 1:04 AM
Thanks for taking the time to submit this to tech support, Rob

Will
Chienworks wrote on 8/7/2010, 4:50 AM
I usually kill ErrorReportLauncher.exe as soon as i've started Vegas 9 or Sound Forge 10.

I don't see sfvstserver.exe running.

A couple of times i've been able to kill FileIOSurrogate.exe while Vegas is launching without killing Vegas. Surprisingly, when i have succeeded at this Vegas is much snappier and more responsive. I wish i could figure out a way to do it reliably every time, but most of the time Vegas simply evaporates too. It makes me wonder if, without it, Vegas is somehow, sometimes able to fall back on previous File IO functionality still included in the base code and this is more efficient than the new stuff in the separate executable.