KGM == Keith G Murphy [EMAIL PROTECTED] writes:
KGM When using a modular mod_perl, I get a huge leak if I preload the 'Pg'
KGM driver in my startup perl script thus:
Hmmm. Interesting theory. I shall have to investigate it. I also
see a multi-megabyte memory leak in my app when DBD::Pg is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, it gets weirder. The following script produces the leak. If I
comment out the install_driver line, I get a big old segfault! Same
if I comment out the Apache::DBI line in addition. This works with
plain apache, or apache-ssl.
Juha-Mikko Ahonen wrote:
I looked into it with the following setup:
apache 1.3.26-0woody1
libapache-mod-perl 1.27-2
postgresql 7.2.1-2woody2
There was a Test.pm module handling all requests for /. It opened a
connection to the database and fetched a couple of rows.
With
Since memory leaks seem to be the topic du jour, I wondered if anyone
else had seen this one:
When using a modular mod_perl, I get a huge leak if I preload the 'Pg'
driver in my startup perl script thus:
#!/usr/bin/perl
use strict;
use Apache::Status ();
use Apache::DBI ();
Using Debian's static-mod_perled apache-perl eliminates the problem.
Do you mean you are using the 'so' version that comes with Debian? You
should be using the static build of apache/mod_perl
Stathy G. Touloumis wrote:
Using Debian's static-mod_perled apache-perl eliminates the problem.
Do you mean you are using the 'so' version that comes with Debian?
Yes, in the case that failed. The package is called 'libapache-mod-perl'.
You
should be using the static build of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 16 October 2002 20:25, Keith G. Murphy wrote:
By should, do you mean that the problems with the loadable module
overall are so well-known that no one in his right mind should ever
use it?
Yes. The problems with DSO mod_perl are well
Hi there,
On Wed, 16 Oct 2002, Keith G. Murphy wrote:
do you mean that the problems with the loadable module overall are
so well-known that no one in his right mind should ever use it?
It's not as bad as that. Significant improvements have been made in
the reliability of mod_perl as DSO and
Ged Haywood wrote:
Hi there,
On Wed, 16 Oct 2002, Keith G. Murphy wrote:
do you mean that the problems with the loadable module overall are
so well-known that no one in his right mind should ever use it?
It's not as bad as that. Significant improvements have been made in
the
Juha-Mikko Ahonen wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 16 October 2002 20:25, Keith G. Murphy wrote:
By should, do you mean that the problems with the loadable module
overall are so well-known that no one in his right mind should ever
use it?
Yes. The
For what it is worth, we use a DSO mod_perl/apache that we compiled ourselves, on
RedHat thought, that is very stable and does not have noticeable memory leaks and have
been using it for over 3 years. Just thought I would throw that out there.
-Original Message-
From: Keith G. Murphy
Hi there,
On Wed, 16 Oct 2002, Keith G. Murphy wrote:
Significant improvements have been made in
the reliability of mod_perl as DSO and nowadays there is much less
discussion about it on this list.
Are you sure it's not because 'most everyone has silently given up on it?
Yes, I'm
Ged Haywood wrote:
Hi there,
On Wed, 16 Oct 2002, Keith G. Murphy wrote:
Significant improvements have been made in
the reliability of mod_perl as DSO and nowadays there is much less
discussion about it on this list.
Are you sure it's not because 'most everyone has silently given up on
On Wed, Oct 16, 2002 at 02:01:33PM -0500, Keith G. Murphy wrote:
Ged Haywood wrote:
Hi there,
On Wed, 16 Oct 2002, Keith G. Murphy wrote:
do you mean that the problems with the loadable module overall are
so well-known that no one in his right mind should ever use it?
It's not as
Daniel Jacobowitz wrote:
On Wed, Oct 16, 2002 at 02:01:33PM -0500, Keith G. Murphy wrote:
My own bug report is now 47 days old, without apparent followup.
Hmmm, I probably should not have posted that. Sounds like a major whine.
That's because I'm having an attack of real life. I haven't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wednesday 16 October 2002 22:52, Keith G. Murphy wrote:
It's not like it was an obvious problem: I only got the DSO to leak
when loading the Pg driver. That's pretty obscure.
Have you tried to connect() without loading the Pg driver first?
[debian-isp readers, to recap, I'm trying to confirm a
memory-leak/segfault problem with Debian stable plus apache(-ssl) plus
libapache-mod-perl. The memory leak happens upon
/etc/init.d/apache(-ssl) reload. You can see my startup script and my
other comments below.]
Juha-Mikko Ahonen
17 matches
Mail list logo
