Return-Path: Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 88004 invoked by uid 500); 19 Jun 2003 22:42:00 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 87989 invoked from network); 19 Jun 2003 22:41:59 -0000 Message-Id: X-Mailer: Novell GroupWise Internet Agent 6.5.1 Date: Thu, 19 Jun 2003 16:41:59 -0600 From: "Brad Nicholes" To: Subject: Cleaning up the bucket allocator in the MPM... Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N After taking a look at how the different MPMs are implemented, it appears that almost all of the MPMs create a bucket allocator and a transaction pool for each worker thread or process. The transaction pool is cleared after each request but the bucket allocator is not cleared or cleaned up until the worker thread or process goes away. Is there a reason why the bucket allocator is never cleaned up? Brad Brad Nicholes Senior Software Engineer Novell, Inc., the leading provider of Net business solutions http://www.novell.com