[Bug 648937] serious memory leak

GStreamer (bugzilla.gnome.org) bugzilla at gnome.org
Wed May 4 03:46:32 PDT 2011


https://bugzilla.gnome.org/show_bug.cgi?id=648937
  GStreamer | gst-plugins-good | 0.10.32

Mark Nauwelaerts <mnauw> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mnauw at users.sourceforge.net

--- Comment #16 from Mark Nauwelaerts <mnauw at users.sourceforge.net> 2011-05-04 10:46:31 UTC ---
The delta-flag issue mentioned in Comment #14 does indeed occur when using
legacyh264parse (which is the one having an access-unit property), but it does
not with the new h264parse.  It would not occur with the older one if also
setting split-packetized=true (and not doing so is messing up its parsing, or
lack thereof for packetized input).

As for Comment #15, not seeing a memory build-up with first pipeline only shows
that whatever method is used to measure is less precise than that matroskamux
is efficient in storing index data, since even with the first pipeline it
should most definitely be accumulating an index that should show up
somewhere/somehow.
As mentioned, the delta-flag issue may affect the magnitude in such a way that
it is brought in measurable range/granularity.

And fwiw, valgrind does not show anything for those pipelines.

-- 
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.


More information about the gstreamer-bugs mailing list