Stas Bekman wrote:
Pringle, Chris (HP-PSG) wrote:
Stas,
I tried the latest version this morning, and it doesn't appear to have
made a great deal of difference. I'm not sure whether it consumes memory
as fast, however, as you said, there are leaks elsewhere. The following
code reproduces it.
: +44 117 31 29664
-Original Message-
From: Stas Bekman [mailto:[EMAIL PROTECTED]
Sent: 11 December 2003 07:44
Cc: Pringle, Chris (HP-PSG); [EMAIL PROTECTED]
Subject: Re: [mp2] Memory Leak
Stas Bekman wrote:
Pringle, Chris (HP-PSG) wrote:
Stas,
I tried the latest version
On Wed, 2003-12-10 at 20:42, Stas Bekman wrote:
Lastly, why does the memory continue to be consumer after the client has
terminated the connection?
Because the server doesn't realize that the connection was aborted. You can
check that with $c-aborted. It could also be a bug in Apache 2.
Raul Dias wrote:
On Wed, 2003-12-10 at 20:42, Stas Bekman wrote:
Lastly, why does the memory continue to be consumer after the client has
terminated the connection?
Because the server doesn't realize that the connection was aborted. You can
check that with $c-aborted. It could also be a bug in
On Thu, 2003-12-11 at 16:30, Stas Bekman wrote:
Raul Dias wrote:
On Wed, 2003-12-10 at 20:42, Stas Bekman wrote:
Lastly, why does the memory continue to be consumer after the client has
terminated the connection?
Because the server doesn't realize that the connection was aborted. You
Raul Dias wrote:
On Thu, 2003-12-11 at 16:30, Stas Bekman wrote:
Raul Dias wrote:
On Wed, 2003-12-10 at 20:42, Stas Bekman wrote:
Lastly, why does the memory continue to be consumer after the client has
terminated the connection?
Because the server doesn't realize that the connection was
On Thu, 2003-12-11 at 20:43, Stas Bekman wrote:
Raul Dias wrote:
On Thu, 2003-12-11 at 16:30, Stas Bekman wrote:
Raul Dias wrote:
On Wed, 2003-12-10 at 20:42, Stas Bekman wrote:
[...]
It would really help to have some section about all the methods
available to $filter, $request and
Raul Dias wrote:
perl-5.8.3-ithread -MApache2 -MModPerl::MethodLookup -e print_object
Apache::RequestRec | wc -l
149
Great. This is a good start point for me.
In that case please see:
http://perl.apache.org/docs/2.0/api/ModPerl/MethodLookup.html#top
I did mean to sound as a rant (if I
On Thu, 2003-12-11 at 22:00, Stas Bekman wrote:
Raul Dias wrote:
I did mean to sound as a rant (if I did). I know that's not easy to
keep with the documentation.
what can you do with your subconscious which seems to tell the truth of what
you've really meant ;)
:)
Doc patches are
Message-
From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
org] On Behalf Of Stas Bekman
Sent: 10 December 2003 02:04
Cc: Pringle, Chris (HP-PSG); [EMAIL PROTECTED]
Subject: Re: [mp2] Memory Leak
Stas Bekman wrote:
Pringle, Chris (HP-PSG) wrote:
Hi,
Apologies
Pringle, Chris (HP-PSG) wrote:
Stas,
I tried the latest version this morning, and it doesn't appear to have
made a great deal of difference. I'm not sure whether it consumes memory
as fast, however, as you said, there are leaks elsewhere. The following
code reproduces it.
Thanks Chris, I'll take
Pringle, Chris (HP-PSG) wrote:
Stas,
I tried the latest version this morning, and it doesn't appear to have
made a great deal of difference. I'm not sure whether it consumes memory
as fast, however, as you said, there are leaks elsewhere. The following
code reproduces it.
[...]
I tested it with
Pringle, Chris (HP-PSG) wrote:
You will find a few comments regarding your code below:
sub handler
{
# Get the filter object
my($f,$bb) = @_;
my $c = $f-c;
You probably don't need $c, you seem to be in the request filter...
# Declare a buffer
my($buffer) = ;
13 matches
Mail list logo
