From owner-freebsd-bugs Tue Jul 10 11: 3: 8 2001 Delivered-To: freebsd-bugs@hub.freebsd.org Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by hub.freebsd.org (Postfix) with ESMTP id 1AE5637B405; Tue, 10 Jul 2001 11:03:06 -0700 (PDT) (envelope-from iedowse@FreeBSD.org) Received: (from iedowse@localhost) by freefall.freebsd.org (8.11.3/8.11.3) id f6AHtHn09356; Tue, 10 Jul 2001 10:55:17 -0700 (PDT) (envelope-from iedowse) Date: Tue, 10 Jul 2001 10:55:17 -0700 (PDT) From: Message-Id: <200107101755.f6AHtHn09356@freefall.freebsd.org> To: geniusj@ods.org, iedowse@FreeBSD.org, freebsd-bugs@FreeBSD.org Subject: Re: kern/23247: FreeBSD 4.2 Active memory usage climbs even when idle. process table cannot make up for it. Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Synopsis: FreeBSD 4.2 Active memory usage climbs even when idle. process table cannot make up for it. State-Changed-From-To: open->closed State-Changed-By: iedowse State-Changed-When: Tue Jul 10 10:33:14 PDT 2001 State-Changed-Why: FreeBSD's memory system is quite complex, so there isn't a direct relationship between the memory used by all processes and the count of "active" memory. The active memory simply refers to pages that are currently on the "active" page queue, and pages can be there for a variety of reasons (I don't know the details). This question appears every now and again; you might find a better answer if you search the mailing list archives. Unless you are seeing the system actually run out of memory unexpectedly, this is almost certainly not a leak. http://www.FreeBSD.org/cgi/query-pr.cgi?pr=23247 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message