Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Prior to this update, some memory was not freed properly by the Evolution code. This update ensures that Evolution code frees all the allocated memory properly, and memory leaks thus no longer occur.
DescriptionVitezslav Humpa
2014-04-04 09:38:50 UTC
Description of problem:
After leaving evolution running overnight, the 'evolution' process jumped to using almost 4GB of memory. I've enabled the 'Automatically synchronize remote mail locally' before that, so this could likely be related, especially since I had evo running for long period of times several times before, never seeing this (though with the version before the multi imapx connections update). The memory went all in evo process, eds seemed okay on memory:
$ ps aux | grep evolution
vhumpa 1040 1.1 49.0 9407568 3884116 ? Sl Apr03 15:37 evolution
vhumpa 2234 0.0 0.0 1194924 3552 ? SLl Mar26 0:56 /usr/libexec/evolution-source-registry
vhumpa 2312 0.0 0.0 1310628 4836 ? Sl Mar26 11:51 /usr/libexec/evolution-addressbook-factory
vhumpa 2319 0.1 0.5 1689096 41084 ? Sl Mar26 23:28 /usr/libexec/evolution-calendar-factory
vhumpa 2363 0.0 0.1 1184276 14108 ? Sl Mar26 0:08 /usr/libexec/evolution/3.8/evolution-alarm-notify
vhumpa 6652 0.6 0.0 0 0 ? Z Mar31 36:02 [evolution] <defunct>
Version-Release number of selected component (if applicable):
evolution-data-server-3.8.5-21.4.el7.x86_64
evolution-3.8.5-20.1.el7.x86_64
Created attachment 884542[details]
evo patch ][
Another take. Interestingly, the leaks from itip are there only under valgrind - some "bad" timing. I did not see any other addressable leaks with this patch, I probably didn't go the same code-path as you did.
Comment 4RHEL Program Management
2014-04-19 05:48:05 UTC
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Created attachment 889221[details]
evo patch ]I[
This is to be applied on top of the evo patch ][. I addressed most of the definitely-lost memory leaks reported in a valgrind log, at least those directly caused by evolution code. There are some from fontconfig and so on, which I do not think I can address within evolution.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://rhn.redhat.com/errata/RHBA-2015-0305.html