Vegas Remaining Active In Task Manager? Heat!

Grazie wrote on 3/17/2015, 10:55 AM

O....K...

Hearing my fans or fan spinning UP and then DOWN, I thought 'allo 'allo. . . what's all this then? I open the PC, check my fan/s and airways for dust and dead bodies, looks ok. . . But where and why the heat?

It's been sometime since I had "Core Temp 1.0" installed, so I gave it go, and read some of the DATA from a year ago - Yikes! Then it was in the 20c to 35c range overall, now today, it's running around the 66 to 69. What's going on? What IS working and for what reason?

I had several fails today with some Audio work I'm doing and decided to close down Vegas13 and restart. Several of these and I get going and finish the work. No worries. I decide to start a NEW veg and I hear this fanny-ing about.

So, I look into MS Task Manager and see 5 sets of VEGAS processes/services still active, even AFTER I'd closed them. Out with the BIG hammer and I manually END their activity.

As I do this, I hear the fans calm down and the CoreTemp readings descend from 69c down to 34c. PC is quiet again. Here's the "facts":-

So, why doesn't/didn't Vegas13 release its activity? What could I have done to end it working? Does this have ramifications for other parts of Vegas? Say Render and BSODs?

Bug?

Grazie

Comments

musicvid10 wrote on 3/17/2015, 11:10 AM

The process always seems to go away after a while for me.

Grazie wrote on 3/17/2015, 11:14 AM

How about 1hour 30 minutes? It was still hanging about.

Grazie

larry-peter wrote on 3/17/2015, 6:57 PM

I've seen 4 or 5 instances of the Vegas process running a few times. I've gotten into the habit of checking that every time I close Vegas.

I've never been able to determine why it happens so randomly. One constant is, anytime I close Vegas and get the error screen after closing - which is probably 10% of the time - the process always has to be killed manually.

I'm now familiar with the performance hit when extra Vegas processes are running - choppy timeline scrolling, weird mouse movements - so I'm in Task Manager frequently hunting for them.

Edit: I have multiple instances of Vegas open many times during a day, and that may play a part in some of them not closing properly.

jetdv wrote on 3/17/2015, 8:32 PM

That is why we always recommend people reboot before installing or uninstalling NewBlue products. Sometimes Vegas remains in memory (with our files locked) even though you've exited Vegas.

johnmeyer wrote on 3/17/2015, 10:31 PM

I've had this happen with all versions of Vegas, starting with Vegas 11. Vegas does a very poor job of cleaning up after itself, and often stays open in the task manager, not just for a few seconds, but indefinitely.

I also sometimes get slow timeline performance which can be cured by closing Vegas, checking task manager and killing it entirely, if needed, restarting, and the re-loading the project.

This is the result of bad programming, not plugins.

I do not have a workaround that I can guarantee will work. However, I have found that if I don't need to leave media open when switching away from Vegas, if I change the preference so that media is NOT released, then Vegas behaves better.

Grazie wrote on 3/18/2015, 1:54 AM

Thanks guys for the "reassurances" - it's kinda good to know that I ain't alone.

However, the stats are in for yesterdays "flip-out" HIGH TEMP as Vegas didn't release:-

154 centigrade! Sure 50 seconds, but 'nuff that could have done damage - yes? - Good to hear/see the Fans kick-in and spin up. But I STILL had to manually kill Vegas.

Grazie

John_Cline wrote on 3/18/2015, 2:27 AM

That had to be some sort of glitch in the software, 154 C (309 F) and that would have absolutely fried the CPU. Your Intel CPU would have shut itself down before that happened. That 7.7 watt reading on your software is highly suspect, too.

Grazie wrote on 3/18/2015, 3:33 AM

Thanks John. Presently the fans are purring along and the "readings" are 37c across the board.

John, can you point me at alternative TEMP s/w? Least ways I could get another view on this.

Cheers

Grazie

RedRob-CandlelightProdctns wrote on 2/23/2022, 8:32 PM

Old thread but the problem STILL exists 7 years later.

On my desktop, I regularly have to kill the still-running Vegas process after existing Vegas Pro 18. (and it's using 13% CPU while not running, but still having a running process)

Dexcon wrote on 2/23/2022, 9:23 PM

As I've mentioned in a couple of other threads on the forum in recent times about the same issue, this problem is not unique to Vegas Pro. Although not currently occurring with Vegas Pro for me, it is currently happening with iZotope's Product Portal, and has happened in past years with Corel PaintShop, Microsoft's Outlook (as well as Outlook Express probably 7 or 8 years ago) and a couple of other programs that don't come to mind at the moment. The problem usually only comes to notice because the program won't open until the 'ghosts' have been cleared from the Task Manager - and the problem has existed over 3 successive desktop computers.

This 2015 post was pre-Windows 10 so likely W8.1 (???) - but it still happens with W10. It's difficult to know exactly where the problem lies: the installed program or Windows. It might be argued that the cause might be Vegas Pro's now rather old programming, but the iZotope Product Portal is not all that many years old and surely has much more modern programming than Vegas Pro. And that it occasionally happens with one of Microsoft's own products - Outlook - is interesting. I wish the problem would go away not only for Vegas Pro but also for all other programs that fall victim to it.

wwaag wrote on 2/23/2022, 10:46 PM

This sits in my taskbar.

It kills all Vegas processes. It's especially useful when Vegas crashes or whenever it hangs during shutdown. It's a lot simpler than opening Task Manager.

It's a free tool and can be downloaded at https://tools4vegas.com/kill-all-vegas/.

There's another tool, SaveCloseKill that's designed specifically for use when Vegas fails to shutdown completely. Here's the link. https://tools4vegas.com/save-close-kill/