You are viewing a plain text version of this content. The canonical link for it is here.
Posted to apache-bugdb@apache.org by Erik MacKinnon <he...@dustcloud.com> on 1999/10/30 17:46:25 UTC

os-windows/5224: 100% CPU Usage

>Number:         5224
>Category:       os-windows
>Synopsis:       100% CPU Usage
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    apache
>State:          open
>Class:          sw-bug
>Submitter-Id:   apache
>Arrival-Date:   Sat Oct 30 08:50:00 PDT 1999
>Last-Modified:
>Originator:     hefe@dustcloud.com
>Organization:
apache
>Release:        1.3.9
>Environment:
Windows NT 4.0 SP5/6
>Description:
Once the Apache service is started, every thing works fine.  After a bit, though, you begin to notice a few things.  The child process is consuming memory at every request, up till a certain amount, and once it gets there, after a bit the CPU use jumps to 100% and stays there.  
>How-To-Repeat:
No idea, try running a Win32 Apache 1.3.9 on a server that gets a lot of traffic, as i get about 25,000 uniques a day and its on a PIII 450.  Maybe it doesn't need to be a lot of traffic, who knows.
>Fix:
I have done everything.  Modded the .conf to high heaven, tried runnin in a console window rather then a service, everything I can think of.  Can't find a way to fix it.
>Audit-Trail:
>Unformatted:
[In order for any reply to be added to the PR database, you need]
[to include <ap...@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!     ]