Description of problem: evolution-exchange-storage seemingly has a memory leak. Version-Release number of selected component (if applicable): evolution-connector-2.8.0-3.fc6 How reproducible: Steps to Reproduce: 1. Start evolution. 2. Subscribe to Microsoft Exchange account using Outlook Web Access. My receive options include check for new mail every 10 minutes, automatically synchronize account locally, apply filters to new messages in Inbox on this server. 3. Wait a few hours... Actual results: Between 15:30 yesterday and 8:00 today the virtual memory size of the evolution-exchange-storage process increased from 680M (big enough, to be frank) to 1225M. On other occasions, I have left it longer and there is no limit to the amount it will gobble. Expected results: No increasing trend in memory use. Additional info: It appears that something is being allocated and not freed every time this process contacts the Exchange server. This probably depends on what is on the server, if you need more information or have particular diagnostic tests you can suggest please contact me. The problem has existed since I first tried using Evolution connector sometime back in RHEL 4. The problem does not seem to occur with version 2.12.0-0ubuntu1 on my Ubuntu box, but I cannot upgrade the evolution version on my RHEL box because gnome-panel needs specific library versions (dependency hell!)
Evolution will be rebased to version 2.12 in the next RHEL5 update, so it sounds like this problem is already taken care of.
Actually no, I found a rather severe memory leak in evolution-exchange-storage that occurs everytime Evolution scans the Exchange folder tree. See: http://bugzilla.gnome.org/show_bug.cgi?id=523023
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-1261.html