Date: Fri, 16 Jan 2004 12:28:58 +0100 From: Alexander Leidinger <Alexander@Leidinger.net> To: Mike Harding <mvh@ix.netcom.com> Cc: ports@freebsd.org Subject: Re: perl 5.8 and malloc (and mod_perl) Message-ID: <20040116122858.278c2527@Magellan.Leidinger.net> In-Reply-To: <20040115233128.BE39954E5@netcom1.netcom.com> References: <20040115233128.BE39954E5@netcom1.netcom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 15 Jan 2004 15:31:28 -0800 (PST)
Mike Harding <mvh@ix.netcom.com> wrote:
>
> (This is a copy of a mail already sent to the perl5.8 port maintainer,
> I wanted to make sure that this info is available to those who run
> into the same issue)
>
> I have a few client sites where recently (since a perl upgrade)
> Mason/mod_perl based httpd processes had 'swollen' to huge sizes -
> 300+ meg. After a lot of coffee and googling and such, it looks like
> the culprit is somehow related to the use of perl's malloc. When
> apache gets a graceful restart signal (for rotating logs) the root
> apache process (and all it's children) grow by 6 megs or so. I'm
> rotating the logs every day at midnight so it took a while for me to
> notice.
I don't know if the situation changed with perl 5.8, but with 5.6 you
have to compile with perls malloc if your application makes use of
signals, else you will see heisenbugs. It isn't safe to call malloc in a
signal handler -- see sigaction(2) -- and a perl program which makes
use of signals may just do this.
Bye,
Alexander.
--
I will be available to get hired in April 2004.
http://www.Leidinger.net Alexander @ Leidinger.net
GPG fingerprint = C518 BC70 E67F 143F BE91 3365 79E2 9C60 B006 3FE7
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040116122858.278c2527>