Andyb01;200744 Wrote: > > > Thanks to the Slimserver tech support in helping isolate the specific > file causing the problem and I then made the link as the next crash was > also a scanned file. > > Hope this helps anyone else having a similar problem
I'm running into exactly the same issue described in this thread - only it's really annoying for me because I generally use the web interface and cover art at work -- of course, where I can't restart the server if it craps out. I've found that it's generally more of a problem when it's loading images and I click on something - an album image, an add to playlist button, etc. But it also seems to crash more often when I'm loading lots of covers on multiple pages in succession. I do have large covers in a lot of my files (800x800 or so - I recently added a couple that were 1200 pixels, but I was having the problem well before these especially large covers), but really prefer it this way, because it's nice to see the cover when you click on an album. Do we think the crashing is related to pixel size or file size? I suppose an option would be to go in and increase the JPG compression on the cover images and see if that helps. 1. But, I guess, the main question is, how do I, as you say slimdevices helped you, track down which images are problematic? I have a good 1500 cover images to deal with here. 2. Has this been reported as a bug? 3. Any suggestions on any way to kickstart the server from a distance when it crashes? I ran services.msc and set it to restart the Slimserver service if it fails, but that clearly hasn't worked. -- Thorphin ------------------------------------------------------------------------ Thorphin's Profile: http://forums.slimdevices.com/member.php?userid=8601 View this thread: http://forums.slimdevices.com/showthread.php?t=29976 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
