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 127098 - static memory cleanup
static memory cleanup
Status: RESOLVED DUPLICATE of bug 64096
Product: glib
Classification: Platform
Component: general
2.2.x
Other All
: Normal minor
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2003-11-16 12:21 UTC by Carsten Burstedde
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4



Description Carsten Burstedde 2003-11-16 12:21:03 UTC
Some glib functions allocate static memory (g_x_error_quark,
g_get_home_dir, etc.).  There is no possibility to free this when glib is
no longer used.  This is mostly an issue when using the glib memory
profiling vtable, because then spurious allocs show up, which means that I
cannot use this information for debugging, which is a pity as the memory
profiling facility is terribly nice.

I would like to have a g_cleanup_everything function or so, to make sure
all memory leaks shown are bugs of my application.  If someone defines the
API, I might implement some of this myself.
Comment 1 Matthias Clasen 2003-11-16 21:28:40 UTC

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