[Bug 700491] [dashdemux] Handle cases where minimumUpdatePeriod sets the period length

[GStreamer (bugzilla.gnome.org)]

https://bugzilla.gnome.org/show_bug.cgi?id=700491
  GStreamer | gst-plugins-bad | git

--- Comment #12 from Olivier Crete (Tester) <olivier.crete at ocrete.ca> 2013-06-10 21:46:07 UTC ---
Even with your patch, it still loops on this:

0:00:02.847825528 21956 0x7fffd80b70f0 LOG                dashdemux
gstdashdemux.c:1394:gst_dash_demux_download_loop:<dashdemux0> Starting download
loop
0:00:02.847831269 21956 0x7fffd80b70f0 DEBUG              dashdemux
gstdashdemux.c:1409:gst_dash_demux_download_loop:<dashdemux0> Next update:
79:12:26.151649481 now: 79:11:48.679422794
0:00:02.847842010 21956 0x7fffd80b70f0 DEBUG              dashdemux
gstdashdemux.c:1534:gst_dash_demux_download_loop:<dashdemux0> download loop 0
0:00:02.847848827 21956 0x7fffd80b70f0 INFO               dashdemux
gstdashdemux.c:1867:gst_dash_demux_get_next_fragment:<dashdemux0> This Period
doesn't contain more fragments for stream 0
0:00:02.847855857 21956 0x7fffd80b70f0 INFO               dashdemux
gstdashdemux.c:1572:gst_dash_demux_download_loop:<dashdemux0> Internal
buffering : 0 s

I'm not sure how the current code is supposed to be stopped in my use-case,
there is one period that is not time bound..

-- 
Configure bugmail: https://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.