2010-05-19, 13:56
If I were to guess, I'd say it's got something to do with that last "ERROR: CLocalizeStrings::ClearBlock" message. Something wants to communicate with the Python thread, but that got killed, so XBMC simply crashes. At any rate, it doesn't appear to get to the stage of actually attempting to launch the game - it fails as soon as Python attempts to shut down.
Running in debug mode slightly slows down XBMC (it has to spam the log and onscreen RAM display). I'm thinking that changes the timing enough for things to "work" (wouldn't be the first time debug mode has made error reproduction impossible, though other factors such as the HDD and skin might also affect matters).
The memory leaks are fairly standard. Good luck finding a debug log referencing Python which doesn't report the things. The amount of RAM available is barely dropping under 30mb (which is plenty by Xbox standards).
Running in debug mode slightly slows down XBMC (it has to spam the log and onscreen RAM display). I'm thinking that changes the timing enough for things to "work" (wouldn't be the first time debug mode has made error reproduction impossible, though other factors such as the HDD and skin might also affect matters).
The memory leaks are fairly standard. Good luck finding a debug log referencing Python which doesn't report the things. The amount of RAM available is barely dropping under 30mb (which is plenty by Xbox standards).