Re: [Zope-dev] Very severe memory leak

2003-08-25 Thread Anthony Baxter
>>> Leonardo Rochael Almeida wrote > Lately this was not enough, however, as Zope started taking more and > more memory, to the point that it frequently required more than one > restart during the day. Note that running with ZEO will at least mean that your server restarts happen a lot faster.

Re: [Zope-dev] Very severe memory leak

2003-08-25 Thread Leonardo Rochael Almeida
On Sat, 2003-08-23 at 22:18, Shane Hathaway wrote: > On 08/22/2003 05:38 PM, Leonardo Rochael Almeida wrote: > > In time, DateTime refcounts eventually dwarves the second place by an > > order of magnitude. I think this is related to the fact that DateTime > > instances are stored as metadata, even

Re: [Zope-dev] Very severe memory leak

2003-08-25 Thread Shane Hathaway
Leonardo Rochael Almeida wrote: On Sat, 2003-08-23 at 22:18, Shane Hathaway wrote: When you flush the cache, those DateTimes should disappear. If they don't, the leak is keeping them. They are disappearing. Too bad they return immediately after, as they're comming from a very heavy catalog query

Re: [Zope-dev] Very severe memory leak

2003-08-25 Thread Paul Winkler
On Mon, Aug 25, 2003 at 02:57:50PM -0400, Shane Hathaway wrote: > 2.6 is also intended to be compatible with Python 2.2. It's just that > here at ZC we haven't gone through the rigorous analysis we've been > planning. Hmm, come to think of it, the community could actually do > that analysis.

Re: [Zope-dev] Very severe memory leak

2003-08-25 Thread Shane Hathaway
Paul Winkler wrote: On Mon, Aug 25, 2003 at 02:57:50PM -0400, Shane Hathaway wrote: 2.6 is also intended to be compatible with Python 2.2. It's just that here at ZC we haven't gone through the rigorous analysis we've been planning. Hmm, come to think of it, the community could actually do tha

RE: [Zope-dev] Very severe memory leak

2003-08-25 Thread Tim Peters
[Paul Winkler] >> Maybe. I'd really like to run with python 2.2. What is involved in >> the "rigorous analysis"? Is there a plan I could follow? [Shane Hathaway] > We need to follow the same process we used to move to Python 2.1. > > http://dev.zope.org/DevHome/Wikis/DevSite/Projects/SupportPython

Re: [Zope-dev] Very severe memory leak

2003-08-25 Thread Shane Hathaway
Tim Peters wrote: I'd actually recommend skipping 2.2 and going straight to 2.3 -- 2.3 is basically 2.2 + 16 months of bugfixes and speedups, a very solid release. It will create more problems for Zope because 2.3 starts complaining about more deprecated practices that 2.2.3 still lets slide, but t

Re: [Zope-dev] Very severe memory leak

2003-08-25 Thread Leonardo Rochael Almeida
On Mon, 2003-08-25 at 15:57, Shane Hathaway wrote: > Leonardo Rochael Almeida wrote: > > On Sat, 2003-08-23 at 22:18, Shane Hathaway wrote: > >>When you flush the cache, those DateTimes should disappear. If they > >>don't, the leak is keeping them. > > > > They are disappearing. Too bad they ret