[doesntcount]

I seem to be encountering an infinite loop in the xbmc code and while I can't say for sure the steps to reproduce, it happens enough that I can try to debug it if required. Before I do, is it a known issue? The backtrace and my hardware are:

XBMC 9.04.1 r20654 (Compiled: May 25, 2009)
My hardware:
Intel Core2 Duo E8400
OS: Ubuntu 9.04
Kernel: 2.6.29-02062906-generic


(gdb) where
#0 0xb7f0f430 in __kernel_vsyscall ()
#1 0xb71fdcf9 in __lll_lock_wait () from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb71f9138 in _L_lock_289 () from /lib/tls/i686/cmov/libpthread.so.0
#3 0xb71f8b76 in pthread_mutex_lock () from /lib/tls/i686/cmov/libpthread.so.0
#4 0xb73ed4b6 in pthread_mutex_lock () from /lib/tls/i686/cmov/libc.so.6
#5 0x08829974 in XCriticalSection::Enter ()
#6 0x0887469b in CSingleLock::Enter ()
#7 0x085b3b21 in CDVDAudio::SetVolume ()
#8 0x082eb515 in CApplication::OnAction ()
#9 0x082ebd53 in CApplication:rocessJoystickEvent ()
#10 0x082ecba4 in CApplication:rocessEventServer ()
#11 0x082ed745 in CApplication::FrameMove ()
#12 0x082972db in CGUIWindowManager:rocess_Internal ()
#13 0x08246fe5 in CGUIDialog:oModal_Internal ()
#14 0x0851c784 in CApplicationMessenger:rocessMessage ()
#15 0x0851d2d4 in CApplicationMessenger::SendMessage ()
#16 0x0851d70f in CApplicationMessenger:oModal ()
#17 0x08246c5f in CGUIDialog:oModal ()
#18 0x082eba00 in CApplication::OnAction ()
#19 0x082ebd53 in CApplication:rocessJoystickEvent ()
#20 0x082ecba4 in CApplication:rocessEventServer ()
#21 0x082ed745 in CApplication::FrameMove ()
#22 0x0853ee53 in CXBApplicationEx::Run ()
#23 0x0853f274 in main ()

[althekiller]

Please see the thread on posting problems in a useful manner...

[doesntcount]

I've been having some trouble reproducing it as reliable as before, but I did get this log file:

http://pastebin.ca/1487692

Not sure exactly when the 100% happened, but I connected the wii remote, navigated to a video, during navigation, sound quit, then when i selected the video, it became unresponsive and top reported 100%. But it may have been 100% before selecting the video.

I'll continue to try to reproduce and provide more info as I learn it. I'll also log top -b info to my own log with timestamp info attached to see if we can maybe better map the 100% incident more precisely with something in the debug log.

[doesntcount]

Also,

Installed from PPA.
Architecture: i686

[althekiller]

Disable the wii remote, it's certainly not helping things. Also, don't snip logs. Anything but a full one is useless.

[colossusr]

hi

i have the same problem when i change tha brightnesss and contrast when a video is playing.

If i set those to 50 and set default for all movies the everything is ok . CPU usage is back to 25-35%

i hope this can help you

colossus

[spiff]

that just means your graphics card does not support the extension we use for adjusting contrast/brightness and hence its emulated in software

[doesntcount]

Useless might be a bit of an exageration, but here's the uncut log nevertheless.

http://pastebin.ca/1489065

I might not be too surprised to learn that the wiiremote has something to do with the crash. I haven't been able to reproduce it with it disabled. Still, an infinite loop is an infinite loop, even if it is wiiremote specific.

Anything else i can provide?

[doesntcount]

I'm able to reproduce this fairly regularly. Is there anything in addition to what I've already provided that can help get to the bottom of this? Is nobody else seeing this issue? I've reproduced the issue once without the wiiremote, so I'm not convinced that it's specific to that.

[althekiller]

It's most certainly something broken with that wii remote crap. It's spewing to the log. Please disable it like I suggested previously.

[doesntcount]

Is the wiiremote client not supported here? Why provide it as a plugin if it's not supported?

[althekiller]

Lets determine whether or not it's the problem, then see about fixing it...

[doesntcount]

So I`ve been absolutely unable to reproduce the problem when I don`t use the wiiremote. So i think it`s fairly safe to assume that it`s to blame. Now that we`ve got that out of the way, any pointers on how to get to the bottom of the issue? Is there a more recent version of the wii-remote plugin that i can try that may have the issue fixed?

Thanks.

[doesntcount]

Looks like this issue has been addressed, as upgrading to the latest PPA (9.04.3) seems to have made the problem go away. Thanks!

[doesntcount]

Crap, I spoke too soon. It was gone for a few days, but it's back again.

Is anybody else having this issue with the wiiuse xbcm-wiiremote-client? I don't think i'm doing anything out of the ordinary to cause an issue unique to my circumstances.

Also, anybody with ideas on how to debug the issue, please provide them.

Also, if the wii-remote client isn't going to be supported, please tell me, so I can stop wasting my time and move to a different input client.