@Birger52Closing iStripper - Quit from menu in taskbar-icon - does not shut program down.
It reduces RAm use to 40Mb, but is still using CPU.
restarting does start another vghd.exe, but doesn't start the interface.
have to shut down 2 instances from Joblist, before program beocmes usable again.
It works correctly for me. If I use Task Manager to monitor the behaviour then using Quit in iStripper's
systray icon then the app first moves from the list of active apps to to the list of background processes and then within a second disappears completely. And I have no difficulty restarting it.
If I use "Close Window" from the active iStripper icon on the main part of the taskbar then it moves from the active App list to the background process list - just as it does if you use the normal window close X icon in the title bar. There is no problem in re-opening it.
In all of the cases the CPU usage by iStripper drops to 0% following the Quit or Close. When the app is active, but with no clips playing, the CPU usage is less than usually less than 1% (most often 0%) with peaks of up to about 3% as I cover and uncover parts of its window, but these peaks only last for a couple of seconds. These measurements were done on a 9 year old laptop, not a souped-up high performance system
It looks like whatever the problem is it is not one that affects all systems, maybe there is something odd about yours that is preventing proper shutdown. What version of Windows are you using?
EDIT: I have just seen from your first post that you are running Windows 7. I suspect that is the root cause of your problem. iStripper should run OK under windows 7, but I am not surprised that there are problems when doing so.