Killing the unkillable process (XP)

UHE is now closed. For Technical Support from Ableton, please go here: http://www.ableton.com/support
Locked
gavspav
Posts: 342
Joined: Tue Jul 12, 2005 12:43 am

Killing the unkillable process (XP)

Post by gavspav » Mon May 25, 2009 7:55 pm

Quite often I found that Live 7 would crash but the process would be unkillable in the Task Manager.

I'd have to reboot in order to run Live.

Now I have the demo of Live 8 on my system - when Live 7 does this I can run Live 8.

Just noticed that when I run it and quit, somewhere along the line, the Live 7 process is killed and I can run Live 7 again *without reboot).

Anyone shed any light on this?

$4mU3l
Posts: 229
Joined: Sun Jan 08, 2006 1:22 pm

Re: Killing the unkillable process (XP)

Post by $4mU3l » Mon May 25, 2009 9:35 pm

This is because the Live 7 process is still in use by another process. The just started Live 8 process is "fresh" and not yet in use by another process. Mostly these processes are started by applications like midi controllers, synths, i.e. any 3rd party application.

Try to quit these other processes first, "Novation Automap" in my case. In the most cases it's possible to quit the crashed Live process via taskmanger without a reboot then.

pwal
Posts: 23
Joined: Fri Jan 04, 2008 9:02 am

Re: Killing the unkillable process (XP)

Post by pwal » Tue May 26, 2009 1:57 pm

could be audio drivers - an external audio interface can be power-cycled, whereas internal needs a reboot...

gavspav
Posts: 342
Joined: Tue Jul 12, 2005 12:43 am

Re: Killing the unkillable process (XP)

Post by gavspav » Tue May 26, 2009 7:07 pm

Thanks - it was probably the audio drivers for me. Foolishly I killed several processes before trying to kill the Live one.

Either my Delta 1010LT or a bundle of Graphics tablet drivers I think.

Locked