[Bug 739419] rtspsrc: not-linked after a while

[GStreamer (GNOME Bugzilla)]

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

--- Comment #79 from Nicola <lists at svrinformatica.it> ---
(In reply to dashesy from comment #77)
> > has you can see the buffer is dropped anyway
> 
> A wrong buffer is dropped as well. cap is set to `pt=96` then this is the
> sequence of received packets:
> 
> 112->112->96->96->...96->112->112->96->96
> 
> The transition from 96 to 112 sets `priv->last_pt = pt;` and the next
> 112->96 wrongly drops the 96 *valid* buffer. 

in my case I have 96->96 ... 96->112->96 and no buffer is dropped, anyway could
you please test the latest patch? This should do the same thing of yours but
hopefully in a way that could be accepted upstream

> 
> > the not-linked error does not happen anymore for me with 1.10 and git master
> 
> You could be right! it takes a long time for it to happen and I have not see
> it with 1.10 either, I thought it is the patch that fixed it. Hard to debug
> infrequent problems.

my old patch make the things more solid anyway, if I manually change the buffer
payload in ptdemux I get a non linked error, this patch

https://cgit.freedesktop.org/gstreamer/gst-plugins-good/commit/?id=608b4ee53c43c3dcbfee167349771eeffd92e071

should make very hard or impossibile to forward a such buffer to ptdemux but
the things can change in future, I wonder why jitterbuffer can request a pt map
and drop the buffer if it return NULL and ptdemux cannot do the same thing

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