Vegas Doesn't Shut Down

ScheffFrog wrote on 4/12/2007, 7:45 AM
When Vegas locks up, and I use Ctrl Alt Del to shut the program down, it does, HOWEVER, if you go into TASKMASTER you will notice that Vegas is STILL RUNNING. Also, if you open Vegas again, have to shut it down because of a problem, then VEGAS is running TWICE in the Taskmaster, and so on and so on. I noticed this because Vegas was having a problem importing a file. After several attempts I went to Taskmaster and found that VEGAS had reopened and was running each time. Vegas was actually running 6 times in Taskmaster!

HELP... why is that. Shouldn't Vegas shut down altogether.

Steve

Comments

rmack350 wrote on 4/12/2007, 8:13 AM
Normally, Vegas would shut down altogether. However, it may be that your particular situation is causing it to hang in this way. You can either wait for it to finish shutting down, or you can try again to force it to quit from the Taskmanager.

While I've never had Vegas do this, I've had Outlook and DreamWeaver do it many times. In DreamWeaver's case it was running some normal cleanup tasks which were taking a long time because of the very large project I had open.

Vegas is quite capable of running 6 times simultaneously. It's a feature of the software.

Rob Mack
dsf wrote on 4/12/2007, 1:22 PM
>>>Frogger777 4/12/2007 8:45:12 AM: “When Vegas locks up, and I use Ctrl Alt Del to shut the program down, it does, HOWEVER, if you go into TASKMASTER you will notice that Vegas is STILL RUNNING. “

CTRL+ALT+DEL calls up Taskmanager/master. But then you say “*if* you go into TASKMASTER…”? It is not clear what you are doing. If you shut a program down using Taskmanager, it can take an annoyingly long time to do so. Perhaps you are opening other copies of Vegas before the current one has shut down? Each time you double-click your Vegas icon, it will open another copy.
jaydeeee wrote on 4/12/2007, 1:40 PM
What's not clear?...he's referring to it taking a long time to shut down (vegas) when killing it in taskman.

It does happen sometimes (far worse with ACID btw - to nightmarish proportions). In taskman bag killing it and do a shut down/reboot instead.
Your sys probably boots faster than waiting for this crap.

rmack350 wrote on 4/12/2007, 2:03 PM
Maybe he's killing it in task manager's Applications tab and then sees it's still running in the Processes tab.

I'm not sure, but I think that "End process" in the Processes tab is a bit more aggressive. "End Task" in the Applications tab always strikes me as "asking nicely".

Rob
jaydeeee wrote on 4/12/2007, 5:15 PM
He stated the problem just fine. No, I'd bet he is killing it in the processes, and it still can/will take a while for it to end.

Just as with Acid, I'd like to see sony look into this random issue.
Opening more instances of Vegas is NOT an answer to this one.
Acid is much worse when it comes to this problem.
rmack350 wrote on 4/12/2007, 6:05 PM
We just had to go through the same process with Premiere (what a surprise) so I got a refresher. Yes, shutting down via the Applications tab seems to just politely ask the program to shut itself down. Doing it through the Processes tab rudely kills the application.

But of course you're right. If a program is seriously hanging then even killing it rudely may not work. And of course opening more instances is just the opposite of shutting down Vegas.

Anyway, the point of it is that when you have to force a program to quit from the Task Manager, you should check the processes tab to make sure it quits. Sometimes a program will appear to quit but hang.

Rob Mack
DJPadre wrote on 4/12/2007, 6:14 PM
No guys, i think youre missing the point..

when V6 or V7 hangs.. (ie driver or codec fault) and then you get that white bar up the top with a not responding message on the windows bar... u then hit the little X to close the app right..
up comes app has failed to respnd, end now or cancel right..
right..

ok so ui end now..
app shuts down all SEEMS good..

now go to task maaanager
Voila, Vegas is still there..

Mine does this too.. it usualy happens when i mess with mutlple codecs or importing defective video clips (such as misfired MPGs with messed up GOP sequences)
dsf wrote on 4/12/2007, 8:53 PM


>>>jaydeeee 4/12/2007 1:40:57 PM: "What's not clear?......he's referring to it taking a long time to shut down (vegas) when killing it in taskman."

It seems reasonable to assume he is not using task manager to shut Vegas down if he says "HOWEVER, if you go into TASKMASTER you will notice that Vegas is STILL RUNNING." OTOH he also said "I use Ctrl Alt Del to shut the program down" which clearly implies he is using task manager to shut down the program. It's called English.

DJPadre wrote on 4/12/2007, 10:17 PM
LOL wow someones having a tanty moment...

as for Vegas.. well if u kill when it locks up, for me, it wont clear off.. in turn taking up pagefile allocated memory, even though its not inuse.

even running Process Explorer (sysinternals.com) doesnt kill it or clear the cache
ScheffFrog wrote on 4/13/2007, 2:35 AM
Actually, I meant to say TaskManager (herein TM)... that was my first mistake. Okay... clearly, I use Crtl, Alt, Del to shut V7 down when I get that horrible white bar that says V7 is NOT responding. ONCE IT IS GONE and I get the screen that asks if I want to report the problem, and I say NO, then is when I go to the TM and in the PROCESSES tab still find V7 running. (I know it is because the cpu memory has kb's that it is using. Now, when I highlight it to END that PROCESS it simply doesn't happen. Or as some of you have said it takes FOREVER and I have never waited much after 10 minutes to see if it would finally shut down.

If I do not REBOOT and start V7 again, and the same problems occur, TM now has TWO V7 programs running. And so on and so on.

Granted REBOOTING ends the trouble. But when you have a problem in V7 the constancy of REBOOTING though it is quite a bit faster than trying to recover everything through TM, it still another bug that could use a fix I think.

Thanks for all of your comments!
Steve
dsf wrote on 4/13/2007, 8:03 PM
I hope you get a response from someone more knowledgeable than me. Judging from your description of the problem, It certainly sounds like something is (hoping you can understand these sophisticated technical terrns) screwed up. I have long since given up on trying to find what driver or registry entry or whatever is the cause of such problems. The first thing to do would be to uninstall then reinstall Vegas. If that doesn’t work, you may need to reformat the drive and reinstall Windows; which, indeed, is a horrible thought.

Vegas is probably the principal program you use. If you have a spare HD you could install another copy of Windows on that and use your BIOS options to boot your computer from that special Vegas drive when you are using Vegas and then reboot from the other drive when you want to use a program on the principal (other) HD. Yes, you would also have to install auxilliary programs you use with Vegas on the Vegas HD. If some screwup happens again with Vegas and you have to reformat/reinstall again at least you will not have to reinstall all your other programs. That’s what I do (which, of course, proves it is the right thing to do.)