JC, as the worlds' primo Windows lion-tamer I wondered if you could suggest a solution for processes that I regularly use but which refuse to fully close.
For some reason the devs haven't implemented a full shut-down when 'exit' is invoked, the dialog disappears but the exe stays active & blocks 're-opening'. Even though it's 'alive' in the proc list, it cannot be accessed to re-open a dialog. :-\
I only discovered this after finding that I couldn't re-open an instance of the prog unless I'd rebooted & then I tracked down why...
ATM PL allows me to quickly find & then RMB terminate, but unfortunately I have a few progs which will only completely only close via this method (or via TaskMan etc). Freeware... but still. :(
So should I use sth like powershell?
Could PL have a list-style implementation + button or similar?
Or?
It sounds like the processes are getting hung during their cleanup. This is happening to more than one app/process? If so, there may be an underlying issue that should be identified.
To be clear, the request is to create a list of processes that are currently in such a hung state for a more accessible way to find and terminate them? Of course, you can multi-select in the main listview and terminate a group of processes, but it sounds like you want something easier to use?
Thanks for the reply JC ;)
This relates to a couple of freeware apps from the same authors.
You are no doubt correct in thinking this is/may be a symptom of something else but as it is just these progs & they work fine otherwise (AFAIK!) I haven't prioritized debugging why...
I have been doing as you say - use the main dialog to search & kill them, but wondered if there was a way PL could police things in that state, first thought being a dialog like the 'app power profile' one where things could be added to police/fast kill.
You have an entry for Ignoring Problem Processes which made me wonder if that is already doing what I need in terms of identification, & could be the logical place for a dialog to identify/list/handle issues.
Basically now I know what they are not doing, I'd like to accelerate the speed with which I can blow them away ;D
Your perspective raises the possibilty of a more in depth diagnostic/policing functionality which could fit the PL features paradigm.
You could definitely use PowerShell for this. A simple script with Stop-Process -Name "processname" -Force would let you kill the lingering process in one click, and you could even create a shortcut to run it. That said, it would be nice if PL offered a "favorite processes" list or a quick-kill button for applications that are known to leave orphaned processes behind.