From owner-freebsd-hackers  Fri Jun 23 18:31:58 1995
Return-Path: hackers-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id SAA03055
          for hackers-outgoing; Fri, 23 Jun 1995 18:31:58 -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 SAA03049
          for <freebsd-hackers@freebsd.org>; Fri, 23 Jun 1995 18:31:57 -0700
Received: (from henrich@localhost) by crh.cl.msu.edu (8.6.11/8.6.9) id VAA00341; Fri, 23 Jun 1995 21:32:37 -0400
From: Charles Henrich <henrich@crh.cl.msu.edu>
Message-Id: <199506240132.VAA00341@crh.cl.msu.edu>
Subject: Re: Memory leak somewhere?
To: roberto@blaise.ibp.fr (Ollivier Robert)
Date: Fri, 23 Jun 1995 21:32:37 -0400 (EDT)
Cc: freebsd-hackers@freebsd.org
In-Reply-To: <199506230854.KAA06398@blaise.ibp.fr> from "Ollivier Robert" at Jun 23, 95 10:54:26 am
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Content-Length: 464       
Sender: hackers-owner@freebsd.org
Precedence: bulk

> Relink the server with either -lgnumalloc or -ldlmalloc (found in
> ports/devel/libdlmalloc). The libc's malloc take as much as two times the
> memory needed per allocation.
>
> I think we should throw away the libc's malloc and adopt another one.

Wow, that worked wonders, my S3 server is small again (well so far) woohoo!

-Crh

    Charles Henrich     Michigan State University     henrich@crh.cl.msu.edu

                     http://rs560.msu.edu/~henrich/