tracking down reference counting memory leaks
mstahl at redhat.com
Tue Oct 21 09:40:50 PDT 2014
On 21.10.2014 18:20, David Tardon wrote:
> 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.
it will of course tell you that your object is leaked. but how do you
know which of the 1968 acquire() calls on it is the cause of the leak?
More information about the LibreOffice