From owner-freebsd-current Sun Jul 16 09:33:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id JAA29355 for current-outgoing; Sun, 16 Jul 1995 09:33:18 -0700 Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id JAA29349 for ; Sun, 16 Jul 1995 09:33:16 -0700 Received: (from henrich@localhost) by crh.cl.msu.edu (8.6.11/8.6.9) id MAA05179; Sun, 16 Jul 1995 12:34:02 -0400 Date: Sun, 16 Jul 1995 12:34:02 -0400 From: Charles Henrich Message-Id: <199507161634.MAA05179@crh.cl.msu.edu> To: davidg@Root.COM, freebsd-current@freebsd.org Subject: Re: XFree86 and swap Newsgroups: lists.freebsd.current References: <3ub86h$qp1@msunews.cl.msu.edu> X-Newsreader: NN version 6.5.0 #3 (NOV) Sender: current-owner@freebsd.org Precedence: bulk In lists.freebsd.current you write: >>> BTW, It stayed at 14MB when I exited Netscape. >> >>Either I'm behind the times, or you are failing to understand a fundamental >>fact about memory allocation under BSD (and IIRC most unices.) >> >>Processes can only ever grow, they can never shrink. > Fundamental? BSD malloc doesn't free memory back to the system, but >GNU malloc and several others do. We plan to switch to one of these other >mallocs (not a GPL'd one) at some point in the future (perhaps 2.2). Unfortunatly in the X server situation, it helps but the server still grows amazingly large over time. Using gnumalloc just increases time. My server grows to 15m within a day of starting it, and stays there :(. -Crh -- Charles Henrich Michigan State University henrich@crh.cl.msu.edu http://rs560.msu.edu/~henrich/