Bugzilla – Bug 9424
Scanner hangs on semi-random file
Last modified: 2008-09-18 08:52:50 UTC
I added a new directory under the root directory of music to be scanned to SqueezeCenter 7.2. When starting to scan the directories by clicking "Basic Settings" - "Look for new and changed music" - "Rescan" the scan process hangs after about 30 seconds. The Status page says: ------------------------------ Directory Scan (1 of 20298) Running 00:05:42 E:\Music\ShareMusic\Download-MP3s\_Pop\ABBA\Gold Greatest Hits\11 Chiquitita.wma SqueezeCenter has finished scanning your music collection. Total Time: 00:05:42 ------------------------------ The file where it hangs changes sometimes. First I thought it's maybe a too long filename, but this doesn't seem to be the case with the above mentioned file. The scanner log has the following output: ------------------------------ [08-09-07 10:02:07.8156] main::main (219) Error: Failed when running main scan: [Can't call method "content_type" on an undefined value at /<C:\PROGRA~1\SQUEEZ~1\server\scanner.exe>Slim/Schema.pm line 1155. ] [08-09-07 10:02:07.8162] main::main (220) Error: Skipping post-process & Not updating lastRescanTime! ------------------------------ The bug can be reproduced every time by me.
Please turn DEBUG on for: (scan.import) - File & Playlist Metadata Import Logging (scan.scanner) - Music & Playlist Folder Scanning then attach the log file to this bug
This seems to be a result of the merge into 7.2, change 22939. I can't lookup where it was done in the branch. For me, I can reproduce this whenever a file doesn't exist. Either referenced from a playlist or from iTunes or MusicIP libraries. a simple check on the status of $track should do it. Change Schema.pm line 115 like so: if (blessed($track)) { $attributeHash->{'CONTENT_TYPE'} = $track->content_type; }
also applies to bug 9442 which was marked as a dupe but is actually a match for this one instead of what it was duped with.
*** This bug has been marked as a duplicate of bug 9434 ***
I believe this is actually a dupe of bug 9432 that has been fixed in the nightly. If you still see this behavior with the nightly please reopen and add additional comments. *** This bug has been marked as a duplicate of bug 9432 ***