[Evolution-hackers] libecal: memory leak
- From: Patrick Ohly <patrick ohly gmx de>
- To: Evolution Hackers <evolution-hackers gnome org>
- Subject: [Evolution-hackers] libecal: memory leak
- Date: Fri, 17 Feb 2012 20:40:16 +0100
Hello!
I've updated one of the chroots for SyncEvolution's nightly testing to
current Debian Testing. Now I am seeing a memory leak in libecal 3.2.2:
==23530== 597 bytes in 15 blocks are definitely lost in loss record
4,401 of 4,550
==23530== at 0x4C27673: malloc (vg_replace_malloc.c:263)
==23530== by 0x7D8AC02: g_malloc (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3000.2)
==23530== by 0x7DA13BD: g_strdup (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3000.2)
==23530== by 0x13BF5CCF: gdbus_proxy_async_method_done (e-gdbus-templates.c:1016)
==23530== by 0x78F7803: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3000.2)
==23530== by 0x7909789: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3000.2)
==23530== by 0x7912E10: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3000.2)
==23530== by 0x7912FB1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3000.2)
==23530== by 0x13BF5438: e_gdbus_proxy_emit_signal (e-gdbus-templates.c:600)
==23530== by 0xC5BE7BB: ffi_call_unix64 (in /usr/lib/x86_64-linux-gnu/libffi.so.5.0.10)
==23530== by 0xC5BE236: ffi_call (in /usr/lib/x86_64-linux-gnu/libffi.so.5.0.10)
==23530== by 0x78F7CC6: g_cclosure_marshal_generic (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3000.2)
==23530== by 0x78F7803: g_closure_invoke (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3000.2)
==23530== by 0x79095BE: ??? (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3000.2)
==23530== by 0x7912E10: g_signal_emit_valist (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3000.2)
==23530== by 0x7912FB1: g_signal_emit (in /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0.3000.2)
==23530== by 0xB82F0FE: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.3000.2)
==23530== by 0xB81D9AD: ??? (in /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0.3000.2)
==23530== by 0x7D840CE: g_main_context_dispatch (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3000.2)
==23530== by 0x7D848C7: ??? (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3000.2)
==23530== by 0x7D84A98: g_main_context_iteration (in /lib/x86_64-linux-gnu/libglib-2.0.so.0.3000.2)
==23530== by 0x13BF36EA: gdbus_proxy_call_sync (e-gdbus-templates.c:1442)
==23530== by 0x13BF72B8: e_gdbus_proxy_call_sync_string__string (e-gdbus-templates.c:1608)
==23530== by 0x1650896A: e_gdbus_cal_call_create_object_sync (e-gdbus-cal.c:571)
==23530== by 0x164DEE15: e_cal_create_object (e-cal.c:3932)
==23530== by 0xFA0B881: SyncEvo::EvolutionCalendarSource::insertItem(std::string const&, std::string const&, bool) (EvolutionCalendarSource.cpp:446)
Does that look familiar to anyone?
--
Bye, Patrick Ohly
--
Patrick Ohly gmx de
http://www.estamos.de/
[
Date Prev][Date Next] [
Thread Prev][Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]