GNOME Bugzilla – Bug 702024
source_camel_registry_types_once() leak
Last modified: 2013-08-09 14:26:01 UTC
OK, I know it only happens once, but still why is it loading a module and then doing nothing but forgetting it? And why is evolution-calendar-factory loading camel stuff anyway? ==21714== 32 bytes in 1 blocks are definitely lost in loss record 2,757 of 7,013 ==21714== at 0x4A08121: calloc (in /usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so) ==21714== by 0x3909E0168F: _dlerror_run (dlerror.c:141) ==21714== by 0x3909E010C0: dlopen@@GLIBC_2.2.5 (dlopen.c:87) ==21714== by 0x376A001830: g_module_open (gmodule-dl.c:99) ==21714== by 0x3DDFA91C3D: camel_provider_load (camel-provider.c:268) ==21714== by 0x3DDFA91E7E: camel_provider_list (camel-provider.c:362) ==21714== by 0x3DDFE41027: source_camel_register_types_once (e-source-camel.c:469) ==21714== by 0x376806C2E7: g_once_impl (gthread.c:624) ==21714== by 0x3DDFE3972B: e_source_init (e-source.c:1722) ==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==
It's because CamelSettings are used all around now, shared between all views. By loading the module the required types should be also added to GLib's types, making them available later.