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 333746 - Memory leak report for gst-ffmpeg
Memory leak report for gst-ffmpeg
Status: RESOLVED INCOMPLETE
Product: GStreamer
Classification: Platform
Component: gst-libav
git master
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-03-07 14:54 UTC by Milosz Derezynski
Modified: 2006-03-15 11:38 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milosz Derezynski 2006-03-07 14:54:46 UTC
This is actually a valgrind log made for BMPx, but it shows a lot of leaks inside gst-ffmpeg, it should be useful i hunting them down.

The log was made with GStreamer CVS as of the date of the bug report as well as GLib 2.10.

The log is far too large to attach it here (approx 1MB), but it's permalinked here (as in, i'm not going to remove it for the next year or so):

http://futurepast.free.fr/bmpx-valgrind.log.bz2
Comment 1 Michael Smith 2006-03-10 15:00:56 UTC
There are a couple of problems with this that make it pretty unlikely anyone will take a real look at it, so here are some suggestions:

  a) run valgrind with --num-callers=xx for some reasonably large xx, the default is too low.
  b) run this with G_SLICE=always-malloc set, so the slice allocator in glib 2.10 doesn't confuse the reports.
  c) trim out the BMPX problems, as having to trudge through several hundred thousand lines of mostly irrelevent things makes these unlikely to get looked at.

Comment 2 Tim-Philipp Müller 2006-03-15 11:38:53 UTC
Just so there's no misunderstanding: we always appreciate reports about memory leaks, but in this case the problem is simply that there's so much information that the report isn't very useful to us.

If you manage to isolate any particular memory leaks in gstreamer, please file a new bug report with just that information :)

Closing this bug for the time being, as there is (IMHO) not much point in keeping it open.