Bug #360
closed
intermediate representation is leaking
Added by Mathieu Desnoyers about 12 years ago.
Updated about 12 years ago.
Assignee:
Julien Desfossez
Description
We have a nice comment in
formats/ctf/metadata/ctf-visitor-generate-io-struct.c
/* TODO: missing metadata "destroy" (memory leak) */
This should be implemented before 1.0 final, especially given that we now expose an external API. It made sense to disregard memory allocation when babeltrace was a one-shot command line converter, but not anymore.
Thorough testing under valgrind is recommended.
- Status changed from New to Resolved
Fixed by commits:
a7af716 fix double-free on error path
6aa249b Add valgrind suppression file for libpopt
41075e7 Fix: unplug memory leak that causes popt-0.13 to segfault
f824ae0 Fix: test all close/fclose ret val, fix double close
cd0058c Fix: fd leak on trace close
9fe26ec Fix memory leaks induced by lack of libpopt documentation
9f2c779 babeltrace: fix poptGetOptArg memleak
95febab plugins: implement plugin unregister
98ef247 callsites: fix memory leak
15d4fe3 Fix: free all the metadata-related memory
6743ae7 Fix : Free the iterator callback arrays
e6d85e3 Fix : cleanup teardown of context
Also available in: Atom
PDF