[imp] process / memory problems in new release (?)

[Chuck Hagenbuch]

Quoting Matthew Dunham <matthew.dunham at ic.ucsb.edu>:

> I've confirmed that these problems don't exist in Horde 3.2.1/IMP 4.2,
> so the trigger is clearly something that's been introduced in the past
> months' development efforts. Just for fun I disabled caching,  
> thinking this new feature might be the culprit -- but no dice.

Which caching feature did you disable? There are a number of different  
ones; several are called out in the accompanying comments as ones that  
increase session size, which might lead to memory growth in httpd  
processes.

-chuck