Bugzilla – Bug 1826
bad playlists can put slimserver into an infinite loop
Last modified: 2008-09-15 14:36:01 UTC
As of change 3507 (really 3508) scanning will follow playlists referenced by other playlists, without dectecting loops. With some bad playlist combinations, this can cause the scanning to go into an infinet loop. Previous to this revision, bad playlists didn't cause noticible issues. Obviously the right thing to do is to fix the bad playlists, but having loop detection might prevent some amount of frustration and bug reports from customers who don't realize they have them. (Especially since most playlists are generated by automated tools.) The simplest test case is an m3u file that refers to itself.
Michael - I've not able to be able reproduce this - I have a m3u file referring to another another m3u file, but parsing stops as normal. Could you upload a specific test case? Thanks.
Pushing this off post 6.1
Created attachment 661 [details] infinite loop playlist
Fixed in subversion change 3795.