GNOME Bugzilla – Bug 702028
e_source_init leak
Last modified: 2013-06-11 16:16:33 UTC
==21714== 188 (16 direct, 172 indirect) bytes in 1 blocks are definitely lost in loss record 5,970 of 7,013 ==21714== at 0x4A08121: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==21714== by 0x376804D996: g_malloc0 (gmem.c:189) ==21714== by 0x3768025A24: g_get_language_names (gcharset.c:562) ==21714== by 0x376803E98B: g_key_file_init (gkeyfile.c:571) ==21714== by 0x376804061C: g_key_file_new (gkeyfile.c:628) ==21714== by 0x3DDFE39782: e_source_init (e-source.c:1733) ==21714== by 0x3CFCC2FA9B: g_type_create_instance (gtype.c:1917) ==21714== by 0x3CFCC14597: g_object_constructor (gobject.c:1855) ==21714== by 0x3CFCC15B18: g_object_newv (gobject.c:1719) ==21714== by 0x3CFCC162E5: g_object_new_valist (gobject.c:1836) ==21714== by 0x3CFD056488: g_initable_new_valist (ginitable.c:227) ==21714== by 0x3CFD05657B: g_initable_new (ginitable.c:149)
That's not a leak. GLib is caching the language names internally. It allocates the strings on the first call and then returns "const gchar * const *".