After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 268246 - Memory usage HIGH exchange calendar
Memory usage HIGH exchange calendar
Status: VERIFIED FIXED
Product: Evolution Exchange
Classification: Deprecated
Component: Connector
2.0.1
Other All
: Normal major
: 2.0.4
Assigned To: Connector Maintainer
Ximian Connector QA
evolution[connector]
Depends on:
Blocks: 270414
 
 
Reported: 2004-10-13 17:50 UTC by Patrick Gibson
Modified: 2005-02-07 05:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Patrick Gibson 2004-10-13 17:50:32 UTC
Please fill in this template when reporting a bug, unless you know what you
are doing.
Description of Problem:


Steps to reproduce the problem:
1. Select calendar using exchange account.
2. 
3. 

Actual Results:
It appears that the connector is loading way too much information from the
exchange database, or there is a memory leak somewhere. My memory footprint
grows from ~30-40 MB to ~1.1GB when I bring up the calendar. 

Coule this be a side-effect of having meeting that are recurring for LONG
periods of time??? 

Expected Results:
I would expect that the memory footprint would be MUCH smaller.  Maybe we
can read only the upcoming day or two or find a better compression of the
data in the calendar so the footprint isn't as large.

How often does this happen? 
Anytime you bring up the calendar with exchange.

Additional Information:
Comment 1 Dave Malcolm 2004-10-13 22:52:28 UTC
Possible duplicate of bug#264403 ?
Comment 2 Patrick Gibson 2004-10-13 22:55:30 UTC
I poked around a bit, and found that when I deleted
~/.evolution/exchange/$account/personal/subfolders/Calendar/cache.ics

The load time for the exchange calendar dropped to nearly nothing and
the memory problem reported within went away.  

I wonder if the cache isn't cleared or something, and the program
always appends to it?  It looks like it might be good to clear that
cache at invocation each time.  
Comment 3 Sarfraaz Ahmed 2004-10-15 06:30:37 UTC
This sounds very similar to 64403 ... Looks like there is some memory
leak happening when the account is actually migrated from 1.4 to 2.0
and the user tries to create a new appointment
Comment 4 Poornima 2005-01-25 11:27:54 UTC
Update to 2.0.3, if still this bug exist reopen this bug, fix for
70414 has fixed this bug
Comment 5 christine 2005-01-27 22:08:32 UTC
is this still a bug? i cannot tell from bug activity..
Comment 6 Patrick Gibson 2005-01-27 22:23:01 UTC
No, I am please with the results.  I had to pick up the patch to
e-cal-backend-exchange.c referenced in 13548, but I am pleased with
the results now.

Thanks,
Patrick 
Comment 7 Sarfraaz Ahmed 2005-01-29 09:46:32 UTC
This has now been fixed.
Comment 8 Poornima 2005-02-07 05:21:43 UTC
Based on reporter comment and the related memory leak  bug is not
reprodicible on 2.0.3 onwards, marking this bug as verified.