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 154515 - Catalogs memory not freed when exiting
Catalogs memory not freed when exiting
Product: glade
Classification: Applications
Component: general
git master
Other All
: Low minor
: ---
Assigned To: Glade 3 Maintainers
Glade 3 Maintainers
Depends on:
Reported: 2004-10-04 23:38 UTC by Shane Butler
Modified: 2018-03-26 14:58 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Shane Butler 2004-10-04 23:38:47 UTC
Chas ( sent this patch a while ago:

> Hi,
> I've noticed that the widget catalogs are loaded but
> never deleted (and glade_catalog_delete() is never
> used).
> This patch tries to fix this nicely by:
> 1) Making glade_catalog_delete a static function.
> 2) Exporting a new function instead:
> glade_catalog_delete_all(), which deletes all of the
> loaded catalogs.
> 3) Saving the catalog list as a local in main() and
> having glade_init() initialize it.
> 4) Having main() call glade_catalog_delete_all() on
> exit.
> I'm aware that this isn't really an important thing
> :-) Anyway, I hope this patch is okay.
> Cheers,
> Chas

The patch is on the original email here:
Comment 1 Vincent Geddes 2007-01-17 00:50:53 UTC
Unfortunately, this patch has bit-rotted a lot since 2004, so we can't hope to apply it. However the bug that this patch address is still a problem (should free all memory before exiting as it helps with valgrind profiles). I am going to leave this bug open and rename it to something more appropriate.
Comment 2 Vincent Geddes 2007-07-01 14:21:17 UTC
I have partially fixed this bug. Still have to unref the widget adaptors though.
Comment 3 GNOME Infrastructure Team 2018-03-26 14:58:45 UTC
-- 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: