Received: (from majordom@localhost) by hyperreal.com (8.8.4/8.8.4) id NAA23609; Fri, 18 Apr 1997 13:24:09 -0700 (PDT) Received: from sierra.zyzzyva.com (ppp01-58.zyzzyva.com [208.214.58.10]) by hyperreal.com (8.8.4/8.8.4) with ESMTP id NAA23587 for ; Fri, 18 Apr 1997 13:24:04 -0700 (PDT) Received: from sierra (localhost [127.0.0.1]) by sierra.zyzzyva.com (8.8.5/8.8.2) with ESMTP id PAA19566 for ; Fri, 18 Apr 1997 15:27:51 -0500 (CDT) Message-Id: <199704182027.PAA19566@sierra.zyzzyva.com> X-Mailer: exmh version 2.0gamma 1/27/96 To: new-httpd@apache.org Subject: Re: Yikes In-reply-to: fielding's message of Fri, 18 Apr 1997 00:26:39 -0700. <9704180026.aa20603@paris.ics.uci.edu> X-uri: http://www.zyzzyva.com/ Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 18 Apr 1997 15:27:51 -0500 From: Randy Terbush Sender: new-httpd-owner@apache.org Precedence: bulk Reply-To: new-httpd@apache.org > Just a guess, but the memory leak is probably due to the example > trace being added to a server or cmd pool instead of a per-request pool. > I guess this is a good example of what not to do in a module. ;-) > Seriously, though, if we can track down which of the handlers is > causing the bloating, it might be worthwhile to check the other modules > to see if the same thing is causing bloat elsewhere. > > .....Roy Roy, Can you expand on what _not_ to do here? I still have a serious growth problem here, and your comments seem to touch on what I am seeing happen.