- May 20, 2008
- 189
- 15
- Home Country
-
Hi guys,
I believe I've identified a small bug, which affects some users, when MediaPortal is set to restart on resume from suspend.
The supporting thread is here.
Briefly, the problem is as follows: the "restart.vbs" script which is used by MediaPortal to restart on resume can use one of two Windows commands to kill the current running MP process - either "tskill" or "taskkill". "tskill" is the first command that the script tries, but if that does not exist then "taskkill" is used.
When "taskkill" is run, it includes a /T parameter - however this parameter tells the running process to also kill all child processes. This appears to cause the script component, which MediaPortal kicked off, to terminate also - therefore, the restart.vbs script stops running and the subsequent command line to start MediaPortal again is never reached.
So, users who have this problem see MediaPortal terminate after a resume from suspend, but it doesn't start again.
It follows that the /T parameter should be removed from the "taskkill" parameters, however this may need to be assessed to determine that there will be no other impact (eg. multiple "orphan" processes that MediaPortal has previously started).
Cheers,
Craig
I believe I've identified a small bug, which affects some users, when MediaPortal is set to restart on resume from suspend.
The supporting thread is here.
Briefly, the problem is as follows: the "restart.vbs" script which is used by MediaPortal to restart on resume can use one of two Windows commands to kill the current running MP process - either "tskill" or "taskkill". "tskill" is the first command that the script tries, but if that does not exist then "taskkill" is used.
When "taskkill" is run, it includes a /T parameter - however this parameter tells the running process to also kill all child processes. This appears to cause the script component, which MediaPortal kicked off, to terminate also - therefore, the restart.vbs script stops running and the subsequent command line to start MediaPortal again is never reached.
So, users who have this problem see MediaPortal terminate after a resume from suspend, but it doesn't start again.
It follows that the /T parameter should be removed from the "taskkill" parameters, however this may need to be assessed to determine that there will be no other impact (eg. multiple "orphan" processes that MediaPortal has previously started).
Cheers,
Craig