Bugzilla – Bug 2640
94% cpu stall during rss news ticker
Last modified: 2008-09-15 14:39:24 UTC
This seems to happen somewhat rarely, and I've been unable to trap anything from the logs when it decidsee to happen. Display seems to stop at the point where a new headline ticker would be just about to start. The top line shows, but no bottom line comes along. other players showing date/time will update every 10-20 seconds, but rss will no longer progress. top shows that slimserver.pl is using 94% cpu. Killing the server takes a long time, even with kill -9 still tracking, and will supply more if I find it.
since fred's timing fix on change 5929, I've been unable to reproduce. closing off.
This appears to be back again. Very intermittent, can't seem to get it to happen when debugging is actually on.
Any luck with this?
unfortunately not. It always seems to be at a point where a new rss feed is about to start scrolling, but tha'ts all I can tell. I've been hoping that the asyncHttp will help. Daily use, I have had to ensure that all my players are off, using datetime screensaver. I have not ever seen this happen with "now playing" scrolling and can happily play music for days on end. This is why I think it has to do with getting the rss feeds.
has there been any other report of this? also, could it be related to scrolling and not rss? possible a specific feed?
It seems to be weather, bbc world, and one of the cbc feeds that I can recall most often. Now playing scrolling during playback never has this problem. I'll try and run some logging and just wait for it to happen again.
ok, this time yahoo music rss. stopped dead, server pages still load, cpu at 44%. Player no longer responding to IR. Timers procedding seemingly normally, but no scrolling text. I'm sorry, but I just can't find anything on this, and I'm wiling to wait it out if I'm the only one.
ran this all last night, and not one stall now with fw 48. I haven't had it last a full night in a very long time (only allowed it this time by accident)
ok, 2 days and not a freeze. marking as fixed. I can always reopen later if this manages to reappear. I'll try to pay more attention in order to find out what change bring it back if it does.