Re: 2.2 in production...

anything more on this?

if memory use stabilized eventually, you can probably just chalk it up
to the Python VM not liking to release memory once it acquires it.

On Mon, 12 Mar 2007 10:33:55 +0200, "Iwan Vosloo" <[email protected]> said:
> Well,
> 
> so far so good, we've been going since late on Friday on 2.2 and we
> don't have any new problems...
> 
> There still is a memory leak though, but much smaller.  It's a bit
> difficult to reproduce since it only happens in a multithreaded
> environment.  The culprit seems to be leaking threading._RLock objects.
> 
> Thanks
> -i

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV