Bugzilla – Bug 413
Crash during music scan
Last modified: 2008-12-18 11:51:16 UTC
I just upgraded to 5.2.0, and the server becomes unresponsive during the music scan. The program keeps running and causing a high load, but it stays stuck on the file below (peter the meter reader). The same mp3 was handled successfully by previous slimserver versoins (5.1.x). Here's the output from --d_scan --d_firmware with settings: useinfocache = 1 useplaylistcache = 1 ... 2004-06-26 21:27:10.5412 index: 249 2004-06-26 21:27:10.5453 itempath: Dr_Demento-Masochism_Tango.mp3 and file:///mp3/+UNSORTED made file:///mp3/+UNSORTED/Dr_Demento-Masochism_Tango.mp3 2004-06-26 21:27:10.7238 isList(file:///mp3/+UNSORTED/Dr_Demento-Masochism_Tango.mp3) == 2004-06-26 21:27:10.7259 not a list: file:///mp3/+UNSORTED/Dr_Demento-Masochism_Tango.mp3 2004-06-26 21:27:10.7276 adding single item: file:///mp3/+UNSORTED/Dr_Demento-Masochism_Tango.mp3, type mp3 2004-06-26 21:27:10.7488 numitems: 1913 2004-06-26 21:27:10.7507 index: 250 2004-06-26 21:27:10.7566 itempath: Dr_Demento-Peter_The_Meter_Reader.mp3 and file:///mp3/+UNSORTED made file:///mp3/+UNSORTED/Dr_Demento-Peter_The_Meter_Reader.mp3 substr outside of string at /usr/local/slimserver//Slim/Formats/MP3.pm line 113, <$fh> line 3. Use of uninitialized value in unpack at /usr/local/slimserver/CPAN/MP3/Info.pm line 1030, <$fh> line 3. substr outside of string at /usr/local/slimserver//Slim/Formats/MP3.pm line 113, <$fh> line 3. Use of uninitialized value in unpack at /usr/local/slimserver/CPAN/MP3/Info.pm line 1030, <$fh> line 3. substr outside of string at /usr/local/slimserver//Slim/Formats/MP3.pm line 113, <$fh> line 3. Use of uninitialized value in unpack at /usr/local/slimserver/CPAN/MP3/Info.pm line 1030, <$fh> line 3. [[ output continues repeating like this indefinately. ]]
Hey DV, I saw the issue with the post. Can you e-mail me the file? dean@slimdevices.com
This was fixed on 2004-06-27, right?
It woudl seem so. marking as fixed. can either be closed or repoened later.
There are 536 bugs in the database with targets of '---' that were fixed prior to new year 2006. I am setting them to targets of 6.2.1 to keep them from showing up in my queries.
Routine bug db maintenance; removing old versions which cause confusion. I apologize for the inconvenience.