GNOME Bugzilla – Bug 348060
Yet another reference debugging tool...
Last modified: 2018-05-24 10:50:56 UTC
A simple Valgrind tool similar in aim to refdbg. The major difference is the introduction of annotations to g_object_(ref|unref) in order to dramatically increase the signal-to-noise ratio. Whilst still imperfect, it already has proven highly effective at pinpointing refleaks in GTK+ and applications... TofO: Most references are paired with an unref that is identifiable at compile-time and this information can be passed to the debugger using a token that is unique to that sequence. The debugger can then automatically suppress known pairs, making the unmatched reference much clearer (ideally, the only remaining reference). Currently, it is in 3 patches. 1) valgrind tool: apply to a valgrind source tree; 2) gobject additions; 3) gtk+ annotations and leak fixes.
Created attachment 69203 [details] [review] refdbg tool
Created attachment 69204 [details] [review] gobject hooks
Created attachment 69205 [details] [review] gtk+ annotations
Created attachment 69206 [details] Sample output for gtk-demo
Created attachment 69207 [details] Sample output for unpatched gtk-demo
As hopefully you are aware, I've split out the easy fixes from the gtk-refdbg.patch. The major one remaining is a shake-down of display/screen disposal.
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/59.