On Tue, 2011-05-17 at 17:52 -0400, Jeff Trawick wrote:


you updated Apache 2.2.x from 2.2.what to 2.2.what?


2.2.17 to 2.2.18. I can however also reproduce the problem in 2.2.17, it seems to be specific to the apr version.

(you updated apr 1.4.2 to 1.4.4)

>
> PID USERNAME    THR PRI NICE   SIZE    RES STATE   C   TIME   WCPU COMMAND
> 11241 www           1 114    0 61492K 11200K CPU0    0   0:53 78.96% httpd
> 11237 www           1 110    0 61492K 11276K RUN     1   0:40 66.26% httpd
> 11238 www           1 108    0 61492K 11276K RUN     0   0:50 56.05% httpd

get syscall trace of high cpu process?
attach with debugger, find callstacks, let it run a while, get
callstacks again, see if there are threads that didn't make useful
progress?


I'm not a programmer but I’ll see what i can get. Any information as to how to do this would be appreciated.

>
> Process takes up all resources and is unresponsive, no errors are logged.

happens immediately, gradually, immediately after some unknown event occurs?


Pretty much right after i start apache the pids start to consume cpu time.