Posts: 26,215
Joined: Oct 2003
Reputation:
187
I think we'll only get decent info if you can get a stack trace (i.e. install GDB).
Posts: 26,215
Joined: Oct 2003
Reputation:
187
Looks likely to be a python 2.7 and/or threading related issue. Your best bet would be to get it reproducible as simply as possible - eg it may be a particular python script that is effected, or it may effect all.
Posts: 2,752
Joined: Dec 2008
Reputation:
23
bobo1on1
cheapass Team-XBMC Developer
Posts: 2,752
Looks like something is trashing the stack or heap, this can be quite difficult to debug, you either need to find the offending code using gdb or valgrind, or find the offending commit using git bisect.
Did you do a git clean -xfd before compiling? Sometimes not everything is recompiled after doing a git pull, it can cause strange things like this.
Posts: 624
Joined: Jun 2009
Reputation:
20
2012-06-06, 04:35
(This post was last modified: 2012-06-06, 04:37 by furii.)
just wanted to chime in that i'm also getting random crashes. unfortunately my previous build was from two weeks ago (5/20ish) so that doesn't really help narrow down which commit might be the offender. i can post a log but i have no clue what to do with gdb. i haven't noticed any crashes when i've been using xbmc but if i leave it idle for a period of time (most recently a few hours) i come back to a crash.
Posts: 42
Joined: Jul 2005
Reputation:
0
How do you revert to a previous commit and which one did you find that doesn't crash.
Posts: 1,250
Joined: Aug 2007
Reputation:
11
Wow that's awesome, didn't know about that.....I've been doing it all manually
Posts: 12,706
Joined: Nov 2003
Reputation:
129
spiff
Team-Kodi Member
Posts: 12,706
if somebody could do a bisect that would be awesome..
Posts: 508
Joined: Aug 2010
2012-06-06, 18:01
(This post was last modified: 2012-06-06, 18:15 by john.doe.)
Yeah there's some form of bug in the python parser right now. Seems to be stack corruption and not actually the script code that's running per se. I.e. you can go into a menu just fine, then leave it, then enter it again and *then* it'll crash, suggesting that it's not python scripts that's at fault, but the actual interpreter.
It also isn't related to *how long* XBMC has been running; but rather, it's the sequence of events.
Example: Start XBMC and enter Movie library, browse around the different movies, play some, etc. All works fine. Now leave the Movie library and go to the Videos library - crash. (just an example). Another example would be entering the Videos library, leaving it, and entering it again. There are all kinds of actions that will cause crashes; the general rule is that the first library you enter will work fine, but after that there's a near 100% risk of crashing when entering another library.
Certain menus don't seem to want to crash, such as the System menu.
Not sure what that implies. Perhaps that it's an issue in the Library code's interfacing with Python, after all the thumbnail caching changes? That's my best theory, as it only seems to be library-accessing modules that can cause a crash.
Anyway, I've been up for 24 hours and need to sleep NOW. If Aenima can do the bisect, that would be great. Install ccache (the compiler cache) to speed up the recompile process tremendously. It won't take you long to do this. Remember to re-run ./bootstrap and ./configure to get it to detect cache and use it for compilation.