Crashes when killing XBMC

[Jupiter]

XBMC on my computer has always been a little buggy, requiring it to sometimes be killed from the process screen.

That would be fine... in fact I was trying to get VoxCommando to make that a little easier for me. But every time I kill XBMC, VoxCommando quits, giving me this message:

Description:
  Stopped working

Problem signature:
  Problem Event Name:   CLR20r3
  Problem Signature 01:   voxcommando.exe
  Problem Signature 02:   1.1.8.3
  Problem Signature 03:   52b6035d
  Problem Signature 04:   XJson
  Problem Signature 05:   0.3.7.0
  Problem Signature 06:   52497e43
  Problem Signature 07:   35
  Problem Signature 08:   10
  Problem Signature 09:   System.NullReferenceException
  OS Version:   6.1.7601.2.1.0.256.1
  Locale ID:   4105

Read our privacy statement online:
  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
  C:\Windows\system32\en-US\erofflps.txt





Trying to kill other processes does not seem to have this challenge. Any thoughts?

[jitterjames]

I will try to recreate this issue here. I imagine it must be something to do with the active TCP connection between VoxCommando and XBMC.  If XBMC is killed forcefully, then this socket could be closing in a way that VC can't handle.

If you don't use playback events from XBMC (for example to announce songs) you could probably disable this connection.  Currently, VC is establishing the connection based on the XBMC focus event and it may also be turned on in the xJSON plugin settings.

[jitterjames]

I was able to reproduce this behaviour, by killing my xbmc task (when the TCP connection was open and listening for events from XBMC), which would cause VC to crash as you described.

Although I'm not sure if I will be able to solve the problem in the program itself, I think I can offer something better.

Next time XBMC crashes you can use the following command in VC.  It will disconnect from XBMC, then kill XBMC and then start XBMC again.

You might need to increase the delay before starting xbmc again, depending on how long it takes to kill the process completely.

Code: [Select]

<?xml version="1.0" encoding="utf-16"?>
<command id="210" name="Reinitialize X B M C" enabled="true" alwaysOn="False" confirm="False" requiredConfidence="0" loop="False" loopDelay="0" loopMax="0" description="">
  <action>
    <cmdType>XJson.Disconnect</cmdType>
    <cmdString />
    <cmdRepeat>1</cmdRepeat>
  </action>
  <action>
    <cmdType>Launch.RawParam</cmdType>
    <cmdString>c:\windows\system32\taskkill.exe&amp;&amp;/F /IM "XBMC.exe"</cmdString>
    <cmdRepeat>1</cmdRepeat>
  </action>
  <action>
    <cmdType>VC.Pause</cmdType>
    <cmdString>1000</cmdString>
    <cmdRepeat>1</cmdRepeat>
  </action>
  <action>
    <cmdType>Launch</cmdType>
    <cmdString>{Path.PFx86}\xbmc\xbmc.exe</cmdString>
    <cmdRepeat>1</cmdRepeat>
  </action>
  <phrase>Reinitialize X B M C</phrase>
</command>