[Bug 752863] New: hlssink: max-files deletes old files without removing them from m3u8 index

[GStreamer (GNOME Bugzilla)]

https://bugzilla.gnome.org/show_bug.cgi?id=752863

            Bug ID: 752863
           Summary: hlssink: max-files deletes old files without removing
                    them from m3u8 index
    Classification: Platform
           Product: GStreamer
           Version: 1.2.4
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: Normal
         Component: gst-plugins-bad
          Assignee: gstreamer-bugs at lists.freedesktop.org
          Reporter: minfrin at sharp.fm
        QA Contact: gstreamer-bugs at lists.freedesktop.org
     GNOME version: ---

When an attempt is made to use the max-files option to limit the number of
files on disk, the first file in the index is deleted too early and is missing:

hlssink max-files=5 location=/var/www/stream/segment%05d.ts
playlist-location=/var/www/stream/output.m3u8
playlist-root=http://192.168.225.2/stream/

root at raspberrypi:/var/www/stream# ls -al; cat output.m3u8 
total 1960
drwxrwxrwt 2 root root    160 Jul 25 14:47 .
drwxr-xr-x 3 root root   4096 Jul 25 10:48 ..
-rw-r--r-- 1 pi   pi      381 Jul 25 14:47 output.m3u8
-rw-r--r-- 1 pi   pi   423940 Jul 25 14:46 segment00066.ts
-rw-r--r-- 1 pi   pi   460788 Jul 25 14:46 segment00067.ts
-rw-r--r-- 1 pi   pi   408712 Jul 25 14:47 segment00068.ts
-rw-r--r-- 1 pi   pi   526024 Jul 25 14:47 segment00069.ts
-rw-r--r-- 1 pi   pi   172032 Jul 25 14:47 segment00070.ts
#EXTM3U
#EXT-X-ALLOW-CACHE:NO
#EXT-X-MEDIA-SEQUENCE:66
#EXT-X-TARGETDURATION:17

#EXTINF:17,ciao
http://192.168.225.2/stream/segment00065.ts
#EXTINF:17,ciao
http://192.168.225.2/stream/segment00066.ts
#EXTINF:17,ciao
http://192.168.225.2/stream/segment00067.ts
#EXTINF:17,ciao
http://192.168.225.2/stream/segment00068.ts
#EXTINF:17,ciao
http://192.168.225.2/stream/segment00069.ts

In the above example the file segment00065.ts is listed in the index, but does
not exist on disk any more. This leads to spurious 404 errors from the
webserver.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.