Bugzilla – Bug 2463
Squeezebox2 crashes while scanning MP3 files (not FLAC)
Last modified: 2009-09-08 09:29:20 UTC
If I repeatedly scan forwards and backwards, over a track boundary, I can get the SB2 to crash totally in anywhere between 2 and 30 seconds. All buttons on the remote are unresponsive. Often after scanning backwards from one track into the previous track, pressing the "FWD" button causes the crash. When I power cycle the SB2, if it comes back up still in backwards scanning mode, it often seems to crash almost immediately. I have verified this on three separate MP3 encoded albums. I have verified that this does NOT happen on three separate FLAC encoded albums.
please provide the crash message from the logs. Also, try grabbing some d_source debugging output from the logs.
Created attachment 978 [details] d_source output of SB2 crash I am not sure I understand what you are saying about a crash message in the logs? However, attached is the d_source debugging output. I started the server, set d_source in the web interface. Then I searched for artist 'A', scrolled down to 'Air', pressed Right ('Moon Safari') then Play. Then when it started playing, I pressed Fwd to go to track 2, then immediately held down Rew to scan backwards. The SB2 crashed immediately (completely unresponsive.) The display shows Now Scanning -2x (2 of 10) [ ] -04:57 Air - Sexy Boy (Moon Safari)
ah, ok. unresponsive is very different from "crashed". If you say 'crash' we expect that you have lost the server and there would be a note in the log as to why it left. frozen is a different matter. d_source log does appear to show nothing glaringly wrong. Is then end of the attachment where it locks up, and nothing more comes or does the log go on after the SB2 freezes? may need some d_slimproto logs for this one, but I'm not able to offer much help on those.
offtopic: I used the word "crash" because the the SB2 requires a power cycle to recover - that is my usual definition. If "becomes unresponsive" is preferred, that's fine. Anyway, the trace stops after the SB2 becomes unresponsive. The problem also exists in the latest nightly build.
Sorry, that was a total lie. Trace *does* continue after the SB2 becomes unresponsive, every 30 seconds, a line like the following comes out: 2005-11-02 20:18:57.7612 Setting maxBitRate for 10.7.2.105 to: 0
not a problem. I was just getting us on the same page :) The maxbitrate line is normal, 0 just means no limiting. If you use the web UI, are you able to get the player to respond? Is the CPU usage looking abnormal? KP, any ideas from support on how to narrow this down?
doing things with the web interface doesn't get the player unstuck... it's quite well hung actually. can't even get it to reset by holding down the power button. i don't think any amount of server-side debug information is going to yield anything useful here... looks like this is in the realm of requiring the debug dongle.
actually just noticed one thing, the axim i'm using has this little jog dial dingus on the left hand side of it that you can use to tab through the links on the page. only one of the links on the album itself works, the add link, but if you try to click it using the stylus it just doesn't do anything...
ERR, sorry, wrong bug
Can you please try the latest nightly with firmware 33? Several lockup situations have been fixed.
*** Bug 2705 has been marked as a duplicate of this bug. ***
*** Bug 3505 has been marked as a duplicate of this bug. ***
Will address in 6.5
Fixed in firmware 55 that is now in test.
This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.