Which uses gdb to track all traces that mutate the reference count and then pairs them up - to throw out most of the noise and (in theory) - this shows you the one guy that unreffed or reffed too much ;-)
At least -that was my gdb assisted solution - that doesn't require code changes.
Prolly ought to be documented in vcl/README.lifecycle =)
Then again - I guess in DBGUTIL mode it'd be great to have something like your tracker included in master Bjoern - ultimately we should chase all of these down, although I suspect that we have a few known leaks still lingering in VCL.
Oh ! the way to track vclptr leaks is using:
https:/ /lists. freedesktop. org/archives/ libreoffice/ 2015-May/ 068067. html
Which uses gdb to track all traces that mutate the reference count and then pairs them up - to throw out most of the noise and (in theory) - this shows you the one guy that unreffed or reffed too much ;-)
At least -that was my gdb assisted solution - that doesn't require code changes.
Prolly ought to be documented in vcl/README. lifecycle =)
Then again - I guess in DBGUTIL mode it'd be great to have something like your tracker included in master Bjoern - ultimately we should chase all of these down, although I suspect that we have a few known leaks still lingering in VCL.
Thanks for chasing this lot though ! =)