Investigating memory leak
Michael Gruner
michael.gruner at ridgerun.com
Sun Feb 20 21:20:27 UTC 2022
Hey Pieter
At a first glance, your app looks fine to me, but here’s a couple of tips I use to hunt for leaks.
You may want to give the leaks tracer a try and see if there are any orphan gobjects left behind:
https://gstreamer.freedesktop.org/documentation/coretracers/leaks.html?gi-language=c
Note that you’ll need to add gst_deinit() to your code and that the tracer will only detect leaks by GStreamer objects not unreffed.
For a more generic leak check you may use Valgrind. Here’s a guide on how to use Valgrind with GStreamer applications:
https://developer.ridgerun.com/wiki/index.php?title=How_to_Analyze_GStreamer_with_Valgrind
Michael
www.ridgerun.com
> On 20 Feb 2022, at 07:44, Pieter Hulshoff via gstreamer-devel <gstreamer-devel at lists.freedesktop.org> wrote:
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20220220/013b41e6/attachment-0001.htm>
More information about the gstreamer-devel
mailing list