Bug 769 – Rescan causes server to crash

Bug 769 - Rescan causes server to crash

Summary:

Rescan causes server to crash

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Tagging
Version:	6.0.0
Platform:	PC Windows XP

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Dan Sully

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2005-01-07 10:04 UTC by Greg Hamilton
Modified:	2008-09-15 14:37 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Greg Hamilton 2005-01-07 10:04:24 UTC

Made a few changes to my library.  Cleaned up a few tags and moved a few files
to be consistant.  Opened SlimServer and pressed rescan.  Server bombs shortly
there  after during the scan.   Here is a snippet of the error with d_info
turned on.

2005-01-07 12:42:16 32005-01-07 12:42:16.1742 CacheItem: Checking status of
file:///O:/My%20Music/Flatt%20&%20Scruggs/Flat%20&%20Scr
uggs%20-%20Greatest%20Hits/%20Dueling%20Banjos.mp3 (TTL: 0).
2005-01-07 12:42:16.1753 deleting
file:///O:/My%20Music/Flatt%20&%20Scruggs/Flat%20&%20Scruggs%20-%20Greatest%20Hits/%20Dueling%20Ba
njos.mp3 from cache as it no longer exists
Can't call method "album" on an undefined value at /PerlApp/Slim/Web/Pages.pm
line 1120.

Both softsqueeze and the webinterface were up and it looks like the troublesome
file was part of the then current playlist.  Once I cleared the playlist. 
Rescan is running.

Comment 1 Dan Sully 2005-01-10 12:31:42 UTC

Greg - was the file that was removed/renamed in a playlist?

Comment 2 Dan Sully 2005-01-10 12:36:31 UTC

Greg - I just checked in what I hope is a fix for this - can you try the most
recent CVS and see if you can reproduce it?

Thanks.

Comment 3 Dan Sully 2005-02-23 11:41:05 UTC

Closing - please reopen if needed.

Comment 4 Chris Owens 2006-06-16 14:40:49 UTC

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.