Return-Path: Delivered-To: apmail-httpd-modules-dev-archive@locus.apache.org Received: (qmail 60818 invoked from network); 16 Jan 2008 17:35:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Jan 2008 17:35:04 -0000 Received: (qmail 87122 invoked by uid 500); 16 Jan 2008 17:34:53 -0000 Delivered-To: apmail-httpd-modules-dev-archive@httpd.apache.org Received: (qmail 87102 invoked by uid 500); 16 Jan 2008 17:34:53 -0000 Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: modules-dev@httpd.apache.org Delivered-To: mailing list modules-dev@httpd.apache.org Received: (qmail 87093 invoked by uid 99); 16 Jan 2008 17:34:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2008 09:34:53 -0800 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [80.229.52.226] (HELO grimnir.webthing.com) (80.229.52.226) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Jan 2008 17:34:26 +0000 Received: from grimnir.webthing.com (localhost [127.0.0.1]) by grimnir.webthing.com (Postfix) with ESMTP id F1A2121C0 for ; Wed, 16 Jan 2008 17:34:29 +0000 (GMT) Date: Wed, 16 Jan 2008 17:34:29 +0000 From: Nick Kew To: modules-dev@httpd.apache.org Subject: Re: httpd process CPU 100% Message-ID: <20080116173429.68b867ab@grimnir> In-Reply-To: <478E3CC2.8010700@gmail.com> References: <478E3CC2.8010700@gmail.com> Organization: WebThing X-Mailer: Sylpheed-Claws 2.5.0-rc3 (GTK+ 2.10.6; i486-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On Wed, 16 Jan 2008 12:20:02 -0500 Christina Fu wrote: > Hi, > > I have a filter module that runs well most of the time, but > occasionally there are a few httpd processes reach and stay cpu 100%. > Any suggestions how to debug this kind of problem? A difficult one to deal with in the abstract. If you can find a particular request that causes it, then recreate it in a debugger and/or profiler. Otherwise maybe try some debug statements in your code. Or indeed, since it's a filter, insert mod_diagnostics and look for anything like an infinite stream of zero-length brigades (unlikely, but ...) -- Nick Kew Application Development with Apache - the Apache Modules Book http://www.apachetutor.org/