The upstream bug was marked won't fix because it was reported against a backend which has been removed. The last comment also indicates that a new bug should be filed with new gstreamer backend. I have tried searching through the gstreamer bugs:
and I see a lot of buffer related bugs that may or may not be related. What also isn't clear is whether this particular bug should be reported against gstreamer or not since it's unclear whether the problem is within gstreamer or in totem's usage there of.
It would be great if someone with more knowledge of the related components could either nail this down or tell us users how we can help nail it down. It should be fairly easy to test this by using low bandwidth connections (or saturating bandwidth with other downloads).
The upstream bug was marked won't fix because it was reported against a backend which has been removed. The last comment also indicates that a new bug should be filed with new gstreamer backend. I have tried searching through the gstreamer bugs:
https:/ /bugzilla. gnome.org/ buglist. cgi?query_ format= specific& order=relevance +desc&bug_ status= __open_ _&product= GStreamer& content= increase+ streaming+ buffer
and I see a lot of buffer related bugs that may or may not be related. What also isn't clear is whether this particular bug should be reported against gstreamer or not since it's unclear whether the problem is within gstreamer or in totem's usage there of.
It would be great if someone with more knowledge of the related components could either nail this down or tell us users how we can help nail it down. It should be fairly easy to test this by using low bandwidth connections (or saturating bandwidth with other downloads).