You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2003/02/12 16:27:41 UTC

DO NOT REPLY [Bug 15380] - httpd 2.0.43 long running processes using lots of CPU until forcibly terminated

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=15380>.
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=15380

httpd 2.0.43 long running processes using lots of CPU until forcibly terminated





------- Additional Comments From trawick@apache.org  2003-02-12 15:27 -------
Please run tusc on a process with high CPU and see what it is doing w.r.t. 
syscalls.

See this document if you aren't familiar with tusc.

http://h21007.www2.hp.com/dspp/tech/tech_TechDocumentDetailPage_IDX/1,1701,2894,00.html

If the high CPU process isn't making syscalls (i.e., looping in user space),
you'll need to attach to it with a debugger and get a backtrace.

Thanks!

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org