From owner-freebsd-hackers  Sat Jun 24 10:32:27 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id KAA18459
          for hackers-outgoing; Sat, 24 Jun 1995 10:32:27 -0700
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id KAA18453
          for <freebsd-hackers@freebsd.org>; Sat, 24 Jun 1995 10:32:25 -0700
Received: from localhost.v-site.net (localhost.v-site.net [127.0.0.1]) by rah.star-gate.com (8.6.11/8.6.9) with SMTP id KAA19358; Sat, 24 Jun 1995 10:32:06 -0700
Message-Id: <199506241732.KAA19358@rah.star-gate.com>
X-Authentication-Warning: rah.star-gate.com: Host localhost.v-site.net didn't use HELO protocol
X-Mailer: exmh version 1.6delta 4/7/95
To: rich@lamprey.utmb.edu
cc: dawes@physics.usyd.edu.au, freebsd-hackers@freebsd.org
Subject: Re: Memory leak somewhere? 
In-reply-to: Your message of "Sat, 24 Jun 1995 09:46:53 CDT."
             <199506241446.JAA03561@id.slip.bcm.tmc.edu> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 24 Jun 1995 10:32:05 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: hackers-owner@freebsd.org
Precedence: bulk

>>> Rich Murphey said:

Howdy Rich,

Long time we don't hear from you :)

I switched to gnumalloc on XF86_S3 and I have not seen any problems.
It is kind of early to report bugs. So far xman is not hugging the
X server's memory, at one point xman managed to make the X server
grow to 20MB over here with libc's malloc. My guess is that there
is a memory leak on the X server. Given that xman exasperates the
problem it may be worth a try to use re-link the X server with
mprof and running xman againt the X server.

At any rate, I like gnu's malloc functionality of giving back to the 
system memory that programs free up.

I recompiled mxterm with gnumalloc and right now  my system feels a bit more 
snappy.


	Tnks,
	Amancio