After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 761925 - Add a destructor to unref singleton
Add a destructor to unref singleton
Status: RESOLVED FIXED
Product: gspell
Classification: Other
Component: general
unspecified
Other All
: Normal enhancement
: ---
Assigned To: gspell maintainers
gspell maintainers
Depends on:
Blocks:
 
 
Reported: 2016-02-12 11:22 UTC by Sébastien Wilmet
Modified: 2016-02-28 13:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sébastien Wilmet 2016-02-12 11:22:18 UTC 
It would be nice to have a destructor to unref the GspellBufferNotifier singleton, to have less garbage in the output of memory-debugging tools.

For example when using gobject-list:
https://blogs.gnome.org/danni/2011/02/17/ld_preload-gobject-lifetime-debugging-tool/
https://git.collabora.com/cgit/user/danni/gobject-list.git/
Comment 1 Sébastien Wilmet 2016-02-28 13:17:47 UTC 
Done. But unfortunately, the output of gobject-list is:

> Still Alive:
>  - 0x2642ca0, GspellBufferNotifier: 1 refs
> 1 objects
>  -- Finalized object 0x2642ca0, GspellBufferNotifier

The singleton is finalized after the gobject-list listing.

But I'm sure that destroying the singleton will simplify the output of other memory debugging tools. And gobject-list can maybe be fixed.