Re: Documentation update request [WAS Re: [mp2] Memory Leak]

2003-12-11 Thread Raul Dias
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 pat

Re: Documentation update request [WAS Re: [mp2] Memory Leak]

2003-12-11 Thread Stas Bekman
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 did).

Re: Documentation update request [WAS Re: [mp2] Memory Leak]

2003-12-11 Thread Raul Dias
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 $fil

Re: Documentation update request [WAS Re: [mp2] Memory Leak]

2003-12-11 Thread Stas Bekman
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 abort

Re: Documentation update request [WAS Re: [mp2] Memory Leak]

2003-12-11 Thread Raul Dias
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 connect

Re: Documentation update request [WAS Re: [mp2] Memory Leak]

2003-12-11 Thread Stas Bekman
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

Re: [mp2] Memory Leak

2003-12-11 Thread Stas Bekman
Hi Got rather a shock this morning when I discovered twenty odd emails in my Inbox!! I can see why open source development moves so fast ;) ;) The version in CVS looks good. It consumes very little memory now, starts off at 0.6%. I think there is still a small leak, it creaps up very slowly at ab

Documentation update request [WAS Re: [mp2] Memory Leak]

2003-12-11 Thread Raul Dias
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 Apa

RE: [mp2] Memory Leak

2003-12-11 Thread Pringle, Chris (HP-PSG)
: +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) wrot

Re: [mp2] Memory Leak

2003-12-11 Thread Stas Bekman
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. Chri

Re: [mp2] Memory Leak

2003-12-10 Thread Stas Bekman
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 t

Re: [mp2] Memory Leak

2003-12-10 Thread Stas Bekman
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

Re: [mp2] Memory Leak

2003-12-10 Thread Pringle, Chris (HP-PSG)
PSG Hewlett-Packard, Bristol Tel: +44 117 31 29664 > -Original 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

Re: [mp2] Memory Leak

2003-12-09 Thread Stas Bekman
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) = ""; my($s

Re: [mp2] Memory Leak

2003-12-09 Thread Stas Bekman
Stas Bekman wrote: Pringle, Chris (HP-PSG) wrote: Hi, Apologies for it not being in the correct format. I wasn't after format but the information ;) Below is a small section of code that I'm having problems with. Thanks for the code sample. It allowed me to single out the guilty element, w

Re: [mp2] Memory Leak

2003-12-09 Thread Stas Bekman
Pringle, Chris (HP-PSG) wrote: Hi, Apologies for it not being in the correct format. I wasn't after format but the information ;) Below is a small section of code that I'm having problems with. Thanks for the code sample. It allowed me to single out the guilty element, which was $f->ctx (I thin

RE: [mp2] Memory Leak

2003-12-09 Thread Pringle, Chris (HP-PSG)
Hi, Apologies for it not being in the correct format. Below is a small section of code that I'm having problems with. Essentially, it puts all the data into a big buffer, and when the buffer hits 500K, it should stop adding data to the buffer, print the buffer out, and decline all further data,