Sune;178522 Wrote: > Hi again, > > Still a good thing with SlimFX. A few bugs seem to be around when using > Mac OS X up against a SB3: > > - Now playing playlist stopped responding after a while (not updated on > computer, not sending added tracks to SB3) > - No tracks showing when clicking on an artist or an album. > > This seems to be connected to "Genre" selection. As soon as any genre > is selected, no more track data are fetched and the "Now Playing" > playlist is no longer accessible. This seems to be a reproducable error > - try select any genre, and see if you can get a track-listing for an > album you haven't track-listed before. > > Note that ordinary "default" web interface was working at all time. > > A restart of my Mac solves the problem for now - can be it would have > been enough to restart the SlimServer. No further details available, > but thought I'd share my experience. This unfortunate error prevents > the SlimFX for being "wife compatible" for now. >
This is kinda surprising. It could easily be explained if the CLI interface could become unresponsive. But that's unlikely, since this probably would have been discovered by now by other control apps. One detail of my implementation (and I'd bet of some other CLI implementations) is that all requests to the server are queued. I.e. one request is sent to the server at a time, and the next request doesn't execute until the first is finished. So if something is not responsive, it may just be the case that some other operation is taking a long time to respond. That said, retrieving Artists/Albums for a Genre doesn't generally take such a long time. (It's usually retrieving a huge playlist that takes a long time and blocks other operations). So this isn't really a plausible explanation either. :-\ It's possible that there's a bug in the way I'm queuing up requests, so that the queue can stop executing at some point. But I've never seen this...I thought that code was very robust. I'll try to get out a version that has a debugging console, which will help. Incidentally, if the client stops responding, you might very well be able to fix the problem by simply re-opening the page in your browser. Reloading the page basically means destroying the previously running version of the app and loading up a new one. You shouldn't need to reboot your server, unless it's a server problem. -- gsamsa ------------------------------------------------------------------------ gsamsa's Profile: http://forums.slimdevices.com/member.php?userid=194 View this thread: http://forums.slimdevices.com/showthread.php?t=32422 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
