Bug XBMC Process Stays alive after being Closed
#1
Hi Everyone,
I believe I have found a bug with the BETA 3 Build of XBMC 13 and I do apologize if I am posting this in the wrong section of the forums as I am new here.

The Issue,
Not always, but about 60% of the time when I close out of XBMC the process appears to be kept alive as if the application is still actively running on my HTPC. This is a major issue as I have integrated everything in with my RTI Control system and it is throwing everything out of whack. The other major symptom that this causes is for WMC7 to not work in live TV as I am using WASPI not Direct Sound in XBMC and this causes playback issues in WMC7 (I assume that XBMC is holding onto my output device when XBMC is still running after it has been closed). Is this an issue that anyone else is experiencing or do I need to provide further information? If it helps I have been an XBMC/WMC7 user for many years and this has never been an issue until Gotham has come about.

Any help would be much appreciated!!!!
Cheers, Kenton
Reply
#2
A debug-log (wiki) would be helpful.
Please read the online manual (wiki) & FAQ (wiki) before posting.

Skins: Estuary | Xperience1080
Opinion: Never purchase HTC products
Reply
#3
I get the same thing from time to time. To the OP, I have added a binding to my AutoHotkey file and bound it to a button on my remote control; it runs the following command, where pskill is one of the Sysinternals utilities:

Run pskill xbmc.exe

This lets me easily kill the zombie XBMC when WMC complains the "files needed to play video aren't installed", IIRC the WMC error message.

Below are the ends of the logfiles I just created, just where they begin to diverge. I am using Aeon Nox Gotham 4.1.9.8, but I've been seeing this problem for several skin and Gotham alpha and beta releases. Sorry, no reliable repro case so far, but just now, it happened when I loaded XBMC, went to my TV show library, selecting an episode, watched for about 5 sec, and quit XBMC.

Hung (taskbar icon gone, but process still alive):

22:56:49 T:2100 NOTICE: StorageServer-2.5.4 Closed down
22:56:50 T:4432 NOTICE: script.tv.show.next.aired: ### xbmc is closing -- stopping background processing
22:56:55 T:8000 ERROR: CPythonInvoker(13, xxx\AppData\Roaming\XBMC\addons\script.videolanguage\default.py): script didn't stop in 5 seconds - let's kill it
22:57:00 T:8000 ERROR: CPythonInvoker(14, xxx\AppData\Roaming\XBMC\addons\script.tv.show.next.aired\default.py): script didn't stop in 5 seconds - let's kill it
(ends here)

Normal (XBMC exited completely):

22:55:46 T:4804 NOTICE: StorageServer-2.5.4 Closed down
22:55:48 T:4384 NOTICE: script.tv.show.next.aired: ### xbmc is closing -- stopping background processing
22:55:48 T:3628 NOTICE: stopped
22:55:48 T:3628 NOTICE: destroy
22:55:48 T:3628 NOTICE: closing down remote control service
22:55:48 T:3628 NOTICE: unload sections
22:55:48 T:3628 NOTICE: special://profile/ is mapped to: special://masterprofile/
22:55:48 T:3628 NOTICE: destroy
22:55:48 T:3628 WARNING: Attempted to remove window 10013 from the window manager when it didn't exist
22:55:48 T:3628 WARNING: Attempted to remove window 10014 from the window manager when it didn't exist
22:55:48 T:3628 WARNING: Attempted to remove window 10015 from the window manager when it didn't exist
22:55:48 T:3628 WARNING: Attempted to remove window 10016 from the window manager when it didn't exist
22:55:48 T:3628 WARNING: Attempted to remove window 10017 from the window manager when it didn't exist
22:55:48 T:3628 WARNING: Attempted to remove window 10018 from the window manager when it didn't exist
22:55:48 T:3628 WARNING: Attempted to remove window 10019 from the window manager when it didn't exist
22:55:48 T:3628 WARNING: Attempted to remove window 10021 from the window manager when it didn't exist
22:55:48 T:3628 WARNING: Attempted to remove window 10107 from the window manager when it didn't exist
22:55:48 T:3628 WARNING: Attempted to remove window 10115 from the window manager when it didn't exist
22:55:48 T:3628 WARNING: Attempted to remove window 10104 from the window manager when it didn't exist
22:55:48 T:3628 NOTICE: closing down remote control service
22:55:48 T:3628 NOTICE: unload sections
22:55:48 T:3628 NOTICE: application stopped...
Reply
#4
Hi Crawfish,
Thankyou for your reply, you seem to be experiencing the exact same thing. Is it worth me posting up a log of my HTPC doing the same thing or will Crawfish's suffice Piers? Is this an issue that can be easily fixed or is it likely to take some time?

Thanks for your help!
Reply
#5
If you are exiting xbmc from a video info screen (versus the top level menu or something like that) then the next-aired part of the problem is probably due to the backend-info-gathering script not getting told that the window it is monitoring is no longer visible. I have a fix for this coming in the next release that you can try out (see the first post in this thread).

I don't know if prior xbmc versions used to ensure that the conditional xbmc.getCondVisibility("Window.IsVisible(10025)") would return invisible when xbmc is shutting down or if this is just a really old bug in script.tv.show.next.aired. I just chose to fix the issue by making the backend part of the script also check xbmc.abortRequested as well (which it probably should have all along).

..wayne..
Reply
#6
This isn't anything new. I've had this problem for years. It seems to happen less often in 13, but still occasionally.

I get the same message
WARNING: Attempted to remove window XXX from the window manager when it didn't exist
Reply

Logout Mark Read Team Forum Stats Members Help
XBMC Process Stays alive after being Closed0