[17-02-13 09:41:18.9572] Slim::Web::Graphics::artworkRequest (80) Artwork request: html/images/Players/softsqueeze_250x250_ffffff.png [17-02-13 09:41:18.9575] Slim::Web::Graphics::artworkRequest (120) Resize specification: 250x250_ffffff.png [17-02-13 09:41:18.9576] Slim::Web::Graphics::artworkRequest (336) Looking for: html/images/Players/softsqueeze.png in skin Default [17-02-13 09:41:18.9622] Slim::Web::Graphics::artworkRequest (375) Resizing: C:\PROGRA~2\SQUEEZ~1\server\HTML\EN\html\images\Players\softsqueeze.png using spec 250x250_ffffff.png [17-02-13 09:41:18.9643] Slim::Utils::Misc::msg (1244) Warning: [09:41:18.9641] Loading image from C:\PROGRA~2\SQUEEZ~1\server\HTML\EN\html\images\Players\softsqueeze.png [17-02-13 09:41:18.9647] Slim::Utils::Misc::msg (1244) Warning: [09:41:18.9646] Resizing from 512x512 png @ 0 to 250x250 png [17-02-13 09:41:18.9942] Slim::Utils::Misc::msg (1244) Warning: [09:41:18.9940] Cached html/images/Players/softsqueeze_250x250_ffffff.png (17257 bytes) [17-02-13 09:41:20.3854] Slim::Utils::Misc::msg (1244) Warning: [09:41:20.3852] Perl interpreter failed at /<C:\PROGRA~2\SQUEEZ~1\server\SQUEEZ~3.EXE>Slim/Utils/GDResizer.pm line 165.
We've seen an increasing number of "Perl interpreter failed at ... GDResizer.pm" over the past year. All Windows. What version?
What makes the least sense to me is the order of the messages logged: the "Cached ..." entry is created _after_ line 165 - where the script supposedly is crashing. How can we successfully cache the data, log the event, if we've crashed already?!?
I'll have to run some tests. -- Michael _______________________________________________ Squeezecenter mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/squeezecenter
