Bugzilla – Bug 15576
Crash after 15-20 mins of Mediafly podcast playback
Last modified: 2019-01-25 10:32:07 UTC
Play any channel / show for about 15-20 mins continously, the UI will crash and perform a number of flashes until it forces reboot. Below is a better description taken from the MF Forum "I am having this issue also. In my case, the player usually has been playing Mediafly content for several hours, then stops. The display flickers, slowly at first, then increases until it is flickering very rapidly and irregularly. By flickering, I mean it switches between displaying different screens. Sometimes a url resembling (trying to recall from my memory) "mediafly://__channel__all__..." flashes by. The player is barely responsive to the controls when it is in this state. It appears to be stuck in a loop where is trying to fetch content over and over. Sometimes after a few minutes or hours of this, it crashes and reboots itself, only to get into the same mode. Holding the power button down until it reboots does not help either, as it does it again after the initialization sequence." I replicated it several times in the afternoon, however now it's not doing it at 6pm cst. Will try again tomorrow morning...
I just got it again, 6:16 pm cst. The problem lies within switching episodes / shows. After finishing it cannot switch and crashes. Or if you play something, go out and switch to play another show, you will also crash it.
You're reporting this against Boom. Did you see it on other players too?
Not seen on other players, just the boom.
Update - you can actually repo this without playing for 15 mins - 1 - Play a show 2 - Switch to another show, and try to play it. (Do that a few times, you will crash)
Had my wife try it on a Boom on February 2. Same thing as reported previously. The error message is: "UNABLE TO RETRIEVE STREAM INFO. Error 416: Requested range is not satisfiable. Stream not retrievable." Seen also on Squeezebox 3. Not reproducible on Squeezebox Radio. Once this happens, the error message will flash momentarily and then always start playing the first podcast, even though you've selected another podcast. Eventually, the error message will not flash if you repeatedly choose the same track; it will still play the first track. The Boom was connected to SbS 7.5.0, the SB3 connected to test.sn.com.
Wasn't like that last week. Not sure what's happening this week.
Also not reproducible on Squeezebox Touch.
While I've seen similar oddities last week, when working on this plugin, I haven't been able to reproduce it today. I have fixed some other issues related to skipping episodes - which might have been related to the issue seen here. If you're running Squeezebox Server, then please update to the latest builds (revision 29990 or later). Are you still able to reproduce this problem?
Today I turned on the boom and it was in this "flashed-out" state. I had to power cycle it a few times to get it stable again. So i've been playing various shows on it all day today, and it did well for about 4 hours. Now it's "flashed-out" again - I was playing a show, didn't touch it, it played the show for about an hour, then tried to autoswitch to the next, and crashed.
I tried it today with a Squeezebox Classic. Was unable to reproduce by switching quickly to play a different podcast. Connected to test.sn.com.
I wonder if this is a network connectivity issue with your wireless router rather than a mediafly issue. We do sometimes have issues with routers. Are you using a wireless connections? If so can you use a wired connection for this test? :)
I do not believe this is due to network oddities here in Mountain View. I've had my wife test on our Boom at home while I test in Mountain View with an SB3, Radio, and Touch. We've done our testing yesterday and today. Yesterday we both saw the problem, and today we both do not.
FYI -- My testing has all been via wired connection, I've been able to crash it easily for the last few days, and yes it's ONLY on the BOOM - all of your other devices that I have (touch, radio, wand thingy) I have NOT seen this issue. Currently I have power cycled my Boom and it's still in the "flashed out" crashed state. I pulled out the plug, waited for 2 min, plugged back in to no avail. It's in a dead loop trying to play something from one of my channels and will not respond to commands. Does anyone know how to factory reset the Boom ? Thanks
OK, if you have something in your playlist that's failing, stop and don't do anything to change the stream. Give me the MAC of your Boom and I'll look up the failing stream, hopefully we can reproduce it then.
For future reference, Boom can be reset by unplugging the power connection, holding down '+' on the remote, and reconnecting power. After the screen displays 'Factory reset...' you can release the '+' button.
mac - 00:04:20:1e:ad:5a the file was in a folder called "test22" form my mediaflyqa account. and, thank you very much for this help :)
Well I can't seem to use your channel URL with my account, so I can't figure out the actual stream. Do you have a way to see the real podcast URL it's trying to play?
http://www.mediafly.com/Podcasts/Feeds/Bill_Moyers_Journal_Audio_PBS
I think it was the bill moyers journal show or http://feeds.pbs.org/pbs/moyers/journal-audio fyi the crash has stopped and I can resume control of my boom...
The latest Bill Moyers episode? The URL for that is http://www.pbs.org/moyers/rss/media/BMJ-1340.mp3 QA: can you try testing this for a bit on Boom? You should be able to just Tune In here, doesn't matter if you use Mediafly.
Just saw it again on SB3 connected to test.sn.com from Mountain View.
Boom crashed again now. Played an episode, finished it and went to switch the next show the channel, crashed. This was in an entirely different channel (health shows). If that helps, not sure.
My theory for now is that we're hitting an issue when it arrives at the end of a channel. I didn't see it yesterday, but did last week. I remember that I was playing my own channels a lot last week, but only popular channels yesterday. And in my own channels there often is only one episode or such. Or has anybody seen this issue with one of the popular channels at all? Will investigate today.
== Auto-comment from SVN commit #7947 to the network repo by michael == == https://svn.slimdevices.com/network?view=revision&revision=7947 == Bug: 15576 Description: don't continue channel switching if there's no other channel
== Auto-comment from SVN commit #7948 to the network repo by michael == == https://svn.slimdevices.com/network?view=revision&revision=7948 == Bug: 15576 Description: don't continue channel switching if there's no other channel
Ok, there indeed was an issue when a channel had fully played. The server tried to fetch the next channel or episode, ignoring if none was returned. It would repeatedly try to fetch the next channel/episode. This should now be fixed on test.mysqueezebox.com. Please note: you'll either have to test this with a SB Touch or use SBS 7.5 to make sure your player is connected to test.mysb.com and _not_ www.mysb.com.
I thought this was an actual crash of the player?
I'm not sure whether the player would crash, or whether the server would go away, cought in a loop.
Not targeted for 7.5.0 and Touch, but definitely an issue to address for Squeezebox Classic and Boom.
Mickey, please pay attention to what you are playing when this happens: an episode out of some channel, a channel, the "All..." item from within this channel?
It was not working and now it's working. Right now it's working. What I would do is: 1. Press Play to play a Mediafly podcast. 2. Once it starts playing, navigate to another podcast. 3. Press Play to play next podcast. It's like it works for awhile, then it doesn't work at all, and then it works. I'm on SbS 7.5 and connected to test.sn.com.
Definitely not happening right now. Tested on Squeezebox Classic. I will close this issue. Please reopen this bug if seen again.