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 690223 - valgrind shows multiple memory leaks on init/deinit even using gst.supp.
valgrind shows multiple memory leaks on init/deinit even using gst.supp.
Status: RESOLVED NOTABUG
Product: GStreamer
Classification: Platform
Component: gstreamer (core)
1.0.3
Other Linux
: Normal normal
: NONE
Assigned To: GStreamer Maintainers
GStreamer Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-12-14 20:16 UTC by Stirling Westrup
Modified: 2013-01-05 16:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28


Attachments
Failed unit-test log showing valgrind output. (51.28 KB, text/plain)
2012-12-14 20:16 UTC, Stirling Westrup
Details

Description Stirling Westrup 2012-12-14 20:16:13 UTC
Created attachment 231590 [details]
Failed unit-test log showing valgrind output.

I have a program that consists of just:

int main(int argc, char *argv[])
  {
    gst_init(&argc,&argv);
    gst_deinit();
    return 0;
  }

When I run this under valgrind, even using the latest gst.supp, I get 59 error, making it difficult to check for my own memory leaks in my code.

Am I doing something wrong here, and if so, is the right way to do it documented anywhere?
Comment 1 Tim-Philipp Müller 2012-12-14 20:23:23 UTC
I think you should just ignore all 'possibly lost', i.e. --show-reachable=no .

You could add suppressions for those as well though.
Comment 2 Tim-Philipp Müller 2013-01-05 16:50:46 UTC
So, as I see it, there's no bug here, but you're welcome to provide patches for gst.supp to suppress these initialisation-related 'possible' leaks. But in general you should just ignore 'possible' leaks anyway.