www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stodd...@apache.org
Subject Re: os-windows/4628: Older DOS-based (16-bit) CGI programs eat memory and eventually fail to execute
Date Tue, 29 Jun 1999 17:42:31 GMT
[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!     ]

Synopsis: Older DOS-based (16-bit) CGI programs eat memory and eventually fail to execute

State-Changed-From-To: open-feedback
State-Changed-By: stoddard
State-Changed-When: Tue Jun 29 10:42:26 PDT 1999
There are known problems with 16-bit CGIs in Apache that will be 
fixed in 1.3.7. Losing memory is not one of the problems we've seen, though.
Can you verify that the system is -really- running out of memory?
How large has apache.exe grown when you see the failure?

In my testing, I observe that apache.exe grows with each request 
until all the threads have been disatched at least once then the process
size stabilizes. Maybe this is what you are seeing.

View raw message