Bug 71 – bad m3u files (with bad volumes) shouldn't hang server

Bug 71 - bad m3u files (with bad volumes) shouldn't hang server

Summary:

bad m3u files (with bad volumes) shouldn't hang server

Status:	RESOLVED FIXED

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Playlists
Version:	unspecified
Platform:	All All

Importance:	P2 minor (vote)
Target Milestone:	---
Assigned To:	KDF

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2003-12-19 21:48 UTC by Blackketter Dean
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 Blackketter Dean 2003-12-19 21:48:45 UTC

M3U files that reference missing volumes can hang the server

Comment 1 KDF 2004-08-04 16:47:42 UTC

does this still happen?  I have tried it out with windows, using 5.3 beta and it
seems to allow a bad volume, and just report filename and default CT for songinfo.

Comment 2 Dan Sully 2005-02-05 10:54:23 UTC

Kevin - whats the status on this?

Comment 3 KDF 2005-02-05 13:22:36 UTC

I'd expect teh db cleanup slimply makes the bad songs disappear.  I recently
fixed an infinite loop in this case.  since I never really saw the exact report
occur, I'm not sure what the proper test case is.

Comment 4 KDF 2005-02-09 12:39:20 UTC

2005-02-09 12:35:01.1092 isFile(N:\mp3\The Joshua Tree\U2 - (04) Bullet The Blue
Sky.mp3) == 0
2005-02-09 12:35:01.1098 Not a song, skipping:
file:///N:/mp3/The%20Joshua%20Tree/U2%20-%20(04)%20Bullet%20The%20Blue%20Sky.mp3

Seems to be fine, web UI reports CT based on extension, uses PlainTitle data. 
No looping or halts.  They can be added to the current playlist, but hte player
will just return to STOP or move on to the next valid song.

I'm willing to call this one fixed.

Comment 5 Chris Owens 2006-06-16 14:41:51 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.