Comment 6 for bug 305428

after 2 days running evolution with no restart or actuin (over the weekend), e-d-s is eating 3G of memory now. It did run under valgrind, but valgrind itself crached when e-d-s terminated, so no traces :-(

The only output i got from it was:
==14646== malloc/free: in use at exit: 991,235,589 bytes in 15,872,136 blocks.
==14646== malloc/free: 61,028,991 allocs, 45,156,855 frees, 5,557,700,510 bytes allocated.
==14646==
==14646== searching for pointers to 15,872,136 not-freed blocks.
==14646== checked 97,791,304 bytes.

right before exit:

$ cat /proc/14646/status
Name: memcheck
State: S (sleeping)
Tgid: 14646
Pid: 14646
PPid: 32068
TracerPid: 0
Uid: 1003 1003 1003 1003
Gid: 2000 2000 2000 2000
FDSize: 1024
Groups: 4 20 24 25 29 30 40 44 46 60 102 105 108 115 118 121 128 129 133 1000 1001 1002 1003 2000 2001 8645 50935 61719
VmPeak: 3940232 kB
VmSize: 3940232 kB
VmLck: 0 kB
VmHWM: 2625868 kB
VmRSS: 2625868 kB
VmData: 3735460 kB
VmStk: 84 kB
VmExe: 1632 kB
VmLib: 18544 kB
VmPTE: 7524 kB
Threads: 11