www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Morshnev <m...@design.ru>
Subject general/4662: Large file - large child size
Date Sun, 27 Jun 1999 16:53:43 GMT

>Number:         4662
>Category:       general
>Synopsis:       Large file - large child size
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sun Jun 27 11:10:00 PDT 1999
>Originator:     moko@design.ru
>Release:        1.3.6
Linux 2.0.36, FreeBSD 2.2.5
It started when we put several .avi files on our server (size about ~20 mb). 
Then I began to see very big apache children in process list.
Short investigation shown that apache child grows as it sends file.

Apache child in "normal" state:
20049 nobody     1   0  1584 1584  1216 S       0  0.0  1.2   0:02 httpd
After I've read 4347 kb of 20mv .avi:
20049 nobody     2   0  5548 5548  5220 S       0  0.7  4.1   0:00 httpd
And so on. 

I've tested several our servers. Problem found only in apache 1.3.6, both 
Linux and FreeBSD. Apache 1.3.4, 1.2.6 no affected.

Apache frees this memory on connection close, so it looks like pool memory leek.
Create a big file and look as apache child size changes while getting it.
I've looked through
but didn't found resons for this behavour.
[In order for any reply to be added to the PR database, you need]
[to include <apbugs@Apache.Org> in the Cc line and make sure the]
[subject line starts with the report component and number, with ]
[or without any 'Re:' prefixes (such as "general/1098:" or      ]
["Re: general/1098:").  If the subject doesn't match this       ]
[pattern, your message will be misfiled and ignored.  The       ]
["apbugs" address is not added to the Cc line of messages from  ]
[the database automatically because of the potential for mail   ]
[loops.  If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request from a  ]
[developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]

View raw message