GNOME Bugzilla – Bug 632135
(Evolution miner) memory leaking
Last modified: 2010-12-09 11:34:44 UTC
As reported in Launchpad bug 654429 (https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/654429) there seems to be a pretty severe memory leak in 2.30.3. Attached to that LP bug is some valgrind diagnostics. I wonder if somebody here could take a look and see if some of the leaks have been plugged, and if so, which commits would have taken care of them. Much thanx!
If desired, I could attach the valgrind logs from the LP bug here, but I'm not sure I see the point. They can be downloaded from LP at: https://bugs.launchpad.net/evolution/+bug/654429/+attachment/1670880/+files/valgrind.tar.gz Cheers.
Moving this to tracker, because it leads the table: ==5887== 92,125,440 bytes in 71,973 blocks are possibly lost in loss record 62,863 of 62,864 ==5887== at 0x4C2815C: malloc (vg_replace_malloc.c:236) ==5887== by 0x66E6C2E: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x66C9A18: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x66C9B17: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x66CB74A: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x66E8B8A: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x66D3B33: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x66ED1F3: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x66ED377: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x66EFBB3: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x66EFC13: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x66EFDA6: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x6737852: ??? (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x672056F: sqlite3_step (in /usr/lib/libsqlite3.so.0.8.6) ==5887== by 0x27F7A94D: ??? (in /usr/lib/evolution/2.30/plugins/liborg-freedesktop-Tracker-evolution-plugin.so) ==5887== by 0x27F7AF49: ??? (in /usr/lib/evolution/2.30/plugins/liborg-freedesktop-Tracker-evolution-plugin.so) ==5887== by 0x27F78609: ??? (in /usr/lib/evolution/2.30/plugins/liborg-freedesktop-Tracker-evolution-plugin.so) ==5887== by 0xCD2173E: ??? (in /lib/libglib-2.0.so.0.2600.0) ==5887== by 0xCD1F7E3: ??? (in /lib/libglib-2.0.so.0.2600.0) ==5887== by 0x8D73970: start_thread (pthread_create.c:304) ==5887== by 0xD07E92C: clone (clone.S:112) ==5887== ==5887== 909,248,614 bytes in 240,306 blocks are possibly lost in loss record 62,864 of 62,864 ==5887== at 0x4C2815C: malloc (vg_replace_malloc.c:236) ==5887== by 0xCCFF304: g_malloc (in /lib/libglib-2.0.so.0.2600.0) ==5887== by 0xCD16D5D: g_strdup (in /lib/libglib-2.0.so.0.2600.0) ==5887== by 0x27F79D7D: ??? (in /usr/lib/evolution/2.30/plugins/liborg-freedesktop-Tracker-evolution-plugin.so) ==5887== by 0x27F7ADDF: ??? (in /usr/lib/evolution/2.30/plugins/liborg-freedesktop-Tracker-evolution-plugin.so) ==5887== by 0x27F7AEEC: ??? (in /usr/lib/evolution/2.30/plugins/liborg-freedesktop-Tracker-evolution-plugin.so) ==5887== by 0x27F7AF49: ??? (in /usr/lib/evolution/2.30/plugins/liborg-freedesktop-Tracker-evolution-plugin.so) ==5887== by 0x27F78609: ??? (in /usr/lib/evolution/2.30/plugins/liborg-freedesktop-Tracker-evolution-plugin.so) ==5887== by 0xCD2173E: ??? (in /lib/libglib-2.0.so.0.2600.0) ==5887== by 0xCD1F7E3: ??? (in /lib/libglib-2.0.so.0.2600.0) ==5887== by 0x8D73970: start_thread (pthread_create.c:304) ==5887== by 0xD07E92C: clone (clone.S:112)
Disabling the plugin meanwhile should help. Please set the proper tracker version.
(In reply to comment #2) > Moving this to tracker, because it leads the table: > ==5887== 92,125,440 bytes in 71,973 blocks are possibly lost in loss record > 62,863 of 62,864 > ==5887== at 0x4C2815C: malloc (vg_replace_malloc.c:236) > ==5887== by 0x66E6C2E: ??? (in /usr/lib/libsqlite3.so.0.8.6) This previous one may be normal, not real memory leaks (marked as possibly lost due to the interior pointers found by valgrind on sqlite memory) > ==5887== > ==5887== 909,248,614 bytes in 240,306 blocks are possibly lost in loss record > 62,864 of 62,864 > ==5887== at 0x4C2815C: malloc (vg_replace_malloc.c:236) > ==5887== by 0xCCFF304: g_malloc (in /lib/libglib-2.0.so.0.2600.0) > ==5887== by 0xCD16D5D: g_strdup (in /lib/libglib-2.0.so.0.2600.0) > ==5887== by 0x27F79D7D: ??? (in > /usr/lib/evolution/2.30/plugins/liborg-freedesktop-Tracker-evolution-plugin.so) This one definitely seems a real memory leak. Not sure if we actually use interior pointers ourselves in Tracker, so don't really know why it's marked as possibly lost.
Setting version to "trunk" from "unspecified", sorry for the spam.
The evolution plugin has been reworked since this bug, closing