tracking down reference counting memory leaks
dtardon at redhat.com
Tue Oct 21 09:20:34 PDT 2014
On Mon, Oct 20, 2014 at 06:27:42PM +0200, Michael Stahl wrote:
> as everyone knows, C++ programs do not leak memory because they use RAII
> and smart pointers to automatically release all allocated memory at just
> the right time.
> ... but enough with the jocularities: there was this ChartModel that was
> leaked due to a uno::Reference cycle, which means that the usual tools
> like valgrind and address sanitizer aren't very useful as such.
I would expect
valgrind --tool=memcheck --leak-check=full --show-leak-kinds=all
to be able to find this. But maybe I do not quite understand the problem.
More information about the LibreOffice