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 76769 - way to free all memory at exit
way to free all memory at exit
Status: RESOLVED DUPLICATE of bug 64096
Product: glib
Classification: Platform
Component: general
2.0.x
Other All
: Normal enhancement
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2002-03-28 14:56 UTC by Morten Welinder
Modified: 2011-02-18 16:13 UTC
See Also:
GNOME target: ---
GNOME version: Unversioned Enhancement


Description Morten Welinder 2002-03-28 14:56:38 UTC 
--enable-gc-friendly (or some other flag) should cause glib to really free
everything allocated by (say) glist.c on exit.

While exit(2) is a very good garbage collector, it does not help in the
quest to find out who leaks what.
Comment 1 Owen Taylor 2002-03-28 16:18:56 UTC 
Freeing all memory at exit has nothing to do with being
"GC friendly" .. "GC friendly" means that we don't keep
live pointers around to dead objects.

A way to free all memory at exit has been requested by
various people, but since it is a complete pain to implement
(you have to basically have some sort of:

 register_cache_freome sort of:

and then use it all over the place) we have no immediate plans
of implementing anything in this area.

See threads starting from:

http://mail.gnome.org/archives/gtk-devel-list/2001-November/msg00279.html
http://mail.gnome.org/archives/gtk-devel-list/2001-November/msg00333.html

In particular, 

http://mail.gnome.org/archives/gtk-devel-list/2001-November/msg00541.html

Has some comments about the dangers to code quality of doing this
in a not well structured fashion.
Comment 2 Owen Taylor 2002-10-15 21:37:11 UTC 

*** This bug has been marked as a duplicate of 64096 ***