GNOME Bugzilla – Bug 523103
Evolution Pango related memory leaks
Last modified: 2010-03-26 05:08:16 UTC
Evolution 2.23.x I have evolution configured with group wise back end and i left it running for an over night. In the morning evolution residential memory consumption went up to 287 MB. Few leaks could be due to dependent packages (glib,pango,gtk) but still i can see leaks in group wise. I closed evolution during collecting valgrind traces (there was no crash).
Created attachment 107507 [details] Valgrind traces of evolution process
Created attachment 109609 [details] Valgrind traces of evolution process I left evolution 2.23.1 running for 2 days/nights. I haven't done any operation during 2 days. Before closing evolution, i did auto completion and switched among components and then forcefully closed evolution (no crash).
Bug 531509 may be helpful
Akhil, Thanks for the traces. I will look into this.
Created attachment 111215 [details] Valgrind traces of evolution process These valgrind traces, i collected with two operations - offline sync and message movement in 2.23.3, could be extension of bug 530543.
Created attachment 111318 [details] Valgrind traces of evolution process After Sankar has fixed a big memory leak, i thought i should try valgrind again. I left evolution running over night without doing any operation and attached are the valgrind traces of evolution 2.23.3. Traces look similar to previous one.
The hunk corresponding to GroupWise is fixed. Rest of the leaks show somewhere in pango etc. Need to dig more. Removing the GW tag.
http://svn.gnome.org/viewvc/evolution-data-server?view=revision&revision=9299
Akhil, maybe worth trying actual 2.23.92 to see how it is going. There could be some changes in leaks hopefully.
see bug 556217
Heh and this is still a problem in evolution-2.24.1.1. I'll try to gather valgrind output too since this is obvious regression since 2.22...
Created attachment 123099 [details] evolution-leaks.txt Well, yes. Seems it looks like leak the most important leak is pango related.
Created attachment 123109 [details] evolution-leaks.txt This one is better as I've installed more libraries with debugging symbols and worked longer in evolution. Also I've checked the following leak: ==3182== 11,779,610 bytes in 6,963 blocks are still reachable in loss record 475 of 475 [snip] ==3182== by 0x4BBA204: pango_ot_ruleset_new_from_description (pango-ot-ruleset.c:299) ==3182== by 0x4BBA419: pango_ot_ruleset_get_for_description (pango-ot-ruleset.c:149) And actually this is not leak and it works as it should. But still somewhere there are big problems...
These traces are obsolete now. I will file a new bug against 2.30.0 if i see memory leaks.