GNOME Bugzilla – Bug 577315
[souphttpsrc] timeout property has no effect
Last modified: 2009-07-16 20:03:47 UTC
The new timeout property of souphttpsrc doesn't work AFAICS. gst-launch-0.10 -v souphttpsrc location=http://stream.wbai.org:8000/24k timeout=10 ! decodebin2 ! autoaudiosink I tried running the above pipeline and dropped the network connection by manipulating the routing table. It's supposed to error out after 10 seconds but it doesn't.
I just retested with debugging, and the property *is* being passed on to the soup session. Bug in libsoup ?
Rene: ping?
It is a bug in libsoup, specifically bug #574414, which seems to be fixed in 2.27. However, it does not seem to fix it completely, at least not so for souphttpsrc, which is now noted (along with possible patch) in bug #588177.
Created attachment 138135 [details] [review] Alternative timeout handling Alternatively, rather than expecting libsoup to (re)act on timeout, one might do some timeout monitoring on souphttpsrc level. The advantage is that it does not depend on libsoup (fix) and is better aware that a timeout has actually occurred. However, since it monitors timeout on a higher level, it might also (theoretically) timeout on a large amount of data/headers over a slow connection where there need not really be a (lower level network) timeout.
I think it's better to depend on the souphttpsrc patch because (as you said) implementing the timeout at our layer has some disadvantages and brings unexpected behaviour. Do you agree? If so, please close this bug :)
I assume you mean(t) the libsoup patch, in which case that is fine by me. So closing as not (our) bug.