Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Date: Wed, 20 Feb 2002 13:47:42 +0100
To: Cocoon Developers Mailing List <cocoon-dev@xml.apache.org>
Subject: Various memory leak fixes
Message-Id: <20020220124741.GA28404@fztig938.bank.dresdner.net>
MIME-Version: 1.0
User-Agent: Mutt/1.3.27i
From: Marcus Crafter <crafterm@fztig938.bank.dresdner.net>
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

Hi All,

	Hope all is well.

	Yesterday Christian and I did some intensive hunting for memory
	leaks inside of our application and Cocoon 2.0.1. We found
	various leaks including:

	1. TraxTransformer's xsltProcessor not releasing it's source resolver.
	2. AbstractTextSerializer not recycling it's namespace pipe.
	3. Logging context retaining the last object model used, per thread.

	In our application these leaks summed to approx. 50-60k per
	request, which under load testing scaled quite quickly.

	Also, FYI, there's currently a known memory leak in Xalan 2.2.0 which
	is also being addressed, Xalan bug 6075.

	I've got a patch ready and will submit it via Bugzilla in the
	next few minutes.

	Cheers,

	Marcus
-- 
        .....
     ,,$$$$$$$$$,      Marcus Crafter
    ;$'      '$$$$:    Computer Systems Engineer
    $:         $$$$:   ManageSoft GmbH
     $       o_)$$$:   82-84 Mainzer Landstrasse
     ;$,    _/\ &&:'   60327 Frankfurt Germany
       '     /( &&&
           \_&&&&'
          &&&&.
    &&&&&&&:

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org