DO NOT REPLY [Bug 11427] - Possible Memory Leak in CGI script invocation

From: <bugzilla(at)apache.org>
Date: Tue Dec 10 2002 - 16:11:37 EST

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11427>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=11427

Possible Memory Leak in CGI script invocation

• Additional Comments From alex@varju.ca 2002-12-10 21:11 ------- I've just checked out the 2.1-dev branch from CVS, and the problem still occurs. The easiest way to reproduce this is to do the following:
  1. Create CGI that sends output to stdout. e.g.:

  #!/usr/bin/perl -I..

  print "Content-type: text/html\n\n";
  for ($i = 0; $i < 2000; $i++)
  {
    printf("%1024s", "asfdasdf");
  }

2. ScriptAlias this script so that it is URL executable.

3. Go to that URL with your browser, and then use the keyboard command to reload the page (e.g. F5 in IE). Hold down the reload key, and you should see a number of processes spawned simultaneously. Let go after 15-20 seconds, and allow the processes to finish. The look at Apache's memory footprint ... it should be larger. Repeat test, watch Apache grow.

---

To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org For additional commands, e-mail: bugs-help@httpd.apache.org Received on Tue Dec 10 21:10:25 2002