Library Update scans weirdly for minutes, then Xbmc CRASHES
#1
Hey,

I've had no problems with Xbmc at all (except for the lovable once-in-a-while crashes). However, this issue baffles me because it just won't change ni matter what I try. I am no expert, but I do know someone here is, and he'd sure know how to figure oit this crash report. Anyway, hope someone can help me. Thanks in advance.

20:38:10 T:2845813568 ERROR: Open - error probing input format, /media/Videos/My Movies/Snatch (2000)/Snatch (2000).avi
20:38:37 T:2956577600 NOTICE: -->Python Interpreter Initialized<--
20:39:21 T:2601491264 NOTICE: VideoInfoScanner: Starting scan ..
20:39:26 T:2601491264 ERROR: Run: Unable to parse web site
20:39:26 T:2601491264 ERROR: GetVideoDetails: Invalid XML file (want <details>)
20:39:29 T:2601491264 NOTICE: VideoInfoScanner: Finished scan. Scanning for video info took 00:08
20:39:37 T:2601491264 NOTICE: VideoInfoScanner: Starting scan ..
20:39:40 T:2601491264 NOTICE: VideoInfoScanner: Finished scan. Scanning for video info took 00:03
20:39:52 T:2845813568 ERROR: Open - error probing input format, /media/Videos/My Movies/Snatch (2000)/Snatch (2000).avi
20:39:56 T:2601491264 NOTICE: VideoInfoScanner: Starting scan ..
20:40:01 T:2601491264 ERROR: GetDirectory - Error getting zip://%2fmedia%2fVideos%2f%24RECYCLE%2eBIN%2fS%2d1%2d5%2d21%2d3188203056%2d4202450647%2d2764439639%2d1001%2f%24IIO145X%2ezip/
20:40:01 T:2601491264 ERROR: GetDirectory - Error getting zip://%2fmedia%2fVideos%2f%24RECYCLE%2eBIN%2fS%2d1%2d5%2d21%2d3188203056%2d4202450647%2d2764439639%2d1001%2f%24I7QMTU9%2ezip/
20:40:01 T:2601491264 ERROR: GetDirectory - Error getting zip://%2fmedia%2fVideos%2f%24RECYCLE%2eBIN%2fS%2d1%2d5%2d21%2d3188203056%2d4202450647%2d2764439639%2d1001%2f%24I6YHRCV%2ezip/
20:40:06 T:2601491264 ERROR: GetDirectory - Error getting zip://%2fmedia%2fVideos%2fD%2dLAP%2fBackup%20Set%202012%2d07%2d05%20234639%2fBackup%20Files%202012%2d08%2d31%20214859%2fBackup%20files%2010%2ezip/
20:40:57 T:2787064640 NOTICE: ES: Client from 192.168.1.65 timed out
20:50:20 T:2265971520 NOTICE: -->Python Interpreter Initialized<--
20:54:05 T:3036968704 ERROR: CWinSystemX11::XErrorHandler: BadDrawable (invalid Pixmap or Window parameter), type:0, serial:281332, error_code:9, request_code:136 minor_code:8
20:54:06 T:3036968704 ERROR: CWinSystemX11::XErrorHandler: BadDrawable (invalid Pixmap or Window parameter), type:0, serial:281334, error_code:9, request_code:136 minor_code:8
20:54:06 T:3036968704 ERROR: CWinSystemX11::XErrorHandler: BadDrawable (invalid Pixmap or Window parameter), type:0, serial:281335, error_code:9, request_code:136 minor_code:8
20:54:06 T:3036968704 ERROR: CWinSystemX11::XErrorHandler: BadDrawable (invalid Pixmap or Window parameter), type:0, serial:281336, error_code:9, request_code:136 minor_code:8
20:54:06 T:3036968704 ERROR: CWinSystemX11::XErrorHandler: BadDrawable (invalid Pixmap or Window parameter), type:0, serial:281337, error_code:9, request_code:136 minor_code:8
20:54:06 T:3036968704 ERROR: CWinSystemX11::XErrorHandler: BadDrawable (invalid Pixmap or Window parameter), type:0, serial:281338, error_code:9, request_code:136 minor_code:8


############### END LOG FILE ################

############ END XBMC CRASH LOG #############
Reply
#2
You need to enable Debug Log ging. In addition, having gdb installed would be useful so we actually get the backtrace, but that's a bonus.
Always read the XBMC online-manual, FAQ and search the forum before posting.
Do not e-mail XBMC-Team members directly asking for support. Read/follow the forum rules.
For troubleshooting and bug reporting please make sure you read this first.


Image
Reply
#3
Thanks jmarshall.

I have done as requested. However, the log file created weighs 251.5 MB and it is surprisingly too much for a single text file. I do not think the pastesites such as http://xbmclogs.com , http://pastebin.com , or http://pastebin.ca will allow me to upload such a huge file. I remind you this is a Library Update issue and so that should be why the text file is so large.

Please advise and thank you.
Reply
#4
Did you remove/rename the old log file before starting a debug session? XBMC just keeps appending to the log so it can get pretty big. I find it hard to believe that a single library update could produce 250 MB of log output.
Reply

Logout Mark Read Team Forum Stats Members Help
Library Update scans weirdly for minutes, then Xbmc CRASHES0