After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 673009 - Video Stream is leaked when playing h264 encoded mkv videos
Video Stream is leaked when playing h264 encoded mkv videos
Status: RESOLVED OBSOLETE
Product: GStreamer
Classification: Platform
Component: gst-libav
0.10.13
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-03-28 16:42 UTC by Benjamin Berg
Modified: 2013-02-23 18:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
last 1000 lines of the valgrind output (88.13 KB, application/octet-stream)
2012-03-28 16:42 UTC, Benjamin Berg
Details

Description Benjamin Berg 2012-03-28 16:42:03 UTC
Created attachment 210796 [details]
last 1000 lines of the valgrind output

When playing .mkv files that contain an h264 video stream, this stream seems to be leaked. The memory usage grew with about 560kB/s, which was similar to the bitrate of the video itself.

This is using the gstreamer0.10-ffmpeg packages from debian-multimedia.org. I have not tried to recompile gstreamer master using jhbuild, but I can do that if it helps.

valgrind only reported a large quantity of still reachable memory, I'll attach part of the output, not sure if it is usefull (it is missing libgstffmpeg.so symbols right now).
Comment 1 Tim-Philipp Müller 2012-06-02 22:37:40 UTC
What's the version of h264parse? There used to be a leak in the parser IIRC.
Comment 2 Benjamin Berg 2012-07-02 14:50:09 UTC
Sorry for the late response ...

I have currently version 0.10.23 installed here, and I am still seeing leaks.

$ dpkg -l | grep gstreamer0.10-plugins-bad
ii  gstreamer0.10-plugins-bad:amd64       0.10.23-6                          GStreamer plugins from the "bad" set
ii  gstreamer0.10-plugins-bad-dbg:amd64   0.10.23-6                          GStreamer plugins from the "bad" set (debug symbols)

Maybe I should try something more recent?
Comment 3 Tim-Philipp Müller 2012-10-17 13:29:43 UTC
No idea, nothing in your valgrind log really sticks out as alarming. (I assume this is a mid-stream snapshot and not after everything got shut down in an orderly way).

I have run some tests with GStreamer 1.0 (git master), and didn't find anything that sticks out either so far.

Perhaps you could re-test with 1.0.x ?
Comment 4 Tim-Philipp Müller 2013-02-23 17:43:16 UTC
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!
Comment 5 Benjamin Berg 2013-02-23 18:11:24 UTC
Just had a quick check (upgraded totem so it uses gst 1.0). Everything looks good now.
Comment 6 Tim-Philipp Müller 2013-02-23 18:18:48 UTC
Great, thanks for checking and following up. I'll change the resolution to OBSOLETE, since we don't know what where and when exactly it was fixed.