Bugzilla – Bug 870
itunes db problem crashes windows service
Last modified: 2008-09-15 14:37:04 UTC
Illegal division by zero at /PerlApp/MP3/Info.pm line 908, <$fh> line 2. this happens within 10 secs of starting the service, every time. after a fresh installation (clearing the sql db and uninstalling slimserver), this happens only after setting the server to use itunes - i don't have any files in the default music folder.
This happened also with 24.2 and 25.2 builds. It seems the itunes database was at fault - by deleting this and creating a new one with a few songs, 26.2 build starts ok. Adding all songs to itunes, then letting slimserver rescan, causes the same crash. There are too many songs to see easily which one might be the problem...
can you start a fresh db using --d_itunes and --d_info. this should show the last song scanned when the application crashes. feel free to attach that last section of the log, and the song in questions.
[now on 27.2 build] it's getting stuck on m4p files - below is the log (repeated several times with new dbs). I removed this song and continued the scan, which stopped on another m4p; and so on. These weren't the only m4p files in the albums where it stopped. 2005-02-27 19:44:56.5821 Updating cache for: file:///G:/tunes/Al%20Green/Call%20 Me/04%20I'm%20so%20Lonesome%20I%20Could%20Cry.m4p Use of uninitialized value in division (/) at /PerlApp/MP3/Info.pm line 907, <$f h> line 2. Illegal division by zero at /PerlApp/MP3/Info.pm line 908, <$fh> line 2.
looks like instead of ignoring m4p files, the server thinks they are mp3 files.
I've been unable to reproduce this by renaming an m4a file. Unfortunately this is all I have. Could you attach one of the problem files?
Created attachment 284 [details] m4p file that crashes service
I've just checked in a fix for this, svn r2257. If you can update you local copy, please try that. Otherwise, it should be in the Feb 28 build.
great, version 2257 works fine
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.