Mailing-List: contact dev-help@perl.apache.org; run by ezmlm
Precedence: bulk
Received-SPF: pass (nike.apache.org: domain of torsten.foertsch@gmx.net
 designates 213.165.64.20 as permitted sender)
From: Torsten Foertsch <torsten.foertsch@gmx.net>
To: dev@perl.apache.org
Subject: Re: Handler leakage
Date: Tue, 3 Mar 2009 09:14:47 +0100
User-Agent: KMail/1.9.10
References: <200903021758.11979.torsten.foertsch@gmx.net>
In-Reply-To: <200903021758.11979.torsten.foertsch@gmx.net>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200903030914.47516.torsten.foertsch@gmx.net>

On Mon 02 Mar 2009, Torsten Foertsch wrote:
> The reason can be found in modperl_handler.c. Each time /handler is
> called a new closure is stored in $PL_modglobal{ANONSUB}{$id}.
> Unfortunately the closure is never deleted from the hash I believe.
> So since $self is in the pad each time /handler is called a reference
> is added to $My::XX from the closure.

Just a thought, I think we must distinguish between 2 cases. A) a 
dynamic handler declared before the interpreters are started and B) a 
dynamic handler declared at runtime.

In the former case the current behavior is perhaps correct. But in the 
latter I think the dynamic handler should bind the interpreter to the 
request/thread just like a pool cleanup does.

Thoughts?

Torsten

-- 
Need professional mod_perl support?
Just hire me: torsten.foertsch@gmx.net

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