GNOME Bugzilla – Bug 690223
valgrind shows multiple memory leaks on init/deinit even using gst.supp.
Last modified: 2013-01-05 16:50:46 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?
I think you should just ignore all 'possibly lost', i.e. --show-reachable=no . You could add suppressions for those as well though.
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.