[Bug 576997] New: Evolution Memory Leak
http://bugzilla.novell.com/show_bug.cgi?id=576997 http://bugzilla.novell.com/show_bug.cgi?id=576997#c0 Summary: Evolution Memory Leak Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: x86-64 OS/Version: openSUSE 11.2 Status: NEW Severity: Normal Priority: P5 - None Component: Evolution AssignedTo: bnc-team-evolution@forge.provo.novell.com ReportedBy: delder@novacoast.com QAContact: lakhil@novell.com Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.7) Gecko/20091222 SUSE/3.5.7-1.1.1 Firefox/3.5.7 If I leave evolution running for more than a day against an IMAP provider and Groupwise (along with a google webcal) it can sometimes consume more than 4 GB of RAM on my system (8 GB RAM total). This seems to be Groupwise related as I didn't get that much memory usage before. I've also encountered high memory usage from eds but I'll save that valgrind trace for another day :) The evolution packages I have installed are: evolution-data-server-debuginfo-2.28.0-2.6.x86_64 evolution-pilot-2.28.0-2.5.x86_64 evolution-exchange-debuginfo-2.28.0-2.5.x86_64 evolution-exchange-2.28.0-2.5.x86_64 evolution-data-server-2.28.0-2.6.x86_64 evolution-2.28.0-2.5.x86_64 evolution-data-server-32bit-2.28.0-2.6.x86_64 evolution-data-server-debuginfo-32bit-2.28.0-2.6.x86_64 evolution-webcal-2.28.0-2.5.x86_64 evolution-webcal-debuginfo-2.28.0-2.5.x86_64 beagle-evolution-0.3.9-9.10.4.x86_64 evolution-debuginfo-2.28.0-2.5.x86_64 evolution-sharp-0.21.1-3.4.x86_64 Reproducible: Always Somehow evolution crashed during the valgrind trace but I think that was a valgrind issue and not evolution as I'm not normally having any evolution crashes. Just let me know what other information I can provide. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576997 http://bugzilla.novell.com/show_bug.cgi?id=576997#c1 --- Comment #1 from Dan Elder <delder@novacoast.com> 2010-02-04 14:14:24 UTC --- The valgrind log is too large (even compressed) to upload but I've posted it to http://www.novacoast.com/valgrind.log.bz2 . Uncompressed it comes out to over 500 MB, sorry about that. The valgrind commands used wer: G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
http://bugzilla.novell.com/show_bug.cgi?id=576997 http://bugzilla.novell.com/show_bug.cgi?id=576997#c2 Dan Elder <delder@novacoast.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #2 from Dan Elder <delder@novacoast.com> 2010-02-11 00:32:50 UTC --- As luck would have it, this particular memory leak in the client appears to have been fixed in the latest build (evolution-2.28.2-0.1.2.x86_64) and I'm no longer able to reproduce the massive memory leak in the current client. I'm sure there are others but the main one which was leaking gigs of memory appears to be gone. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com