From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9606081839.AA11488@clio.rice.edu>
Subject: Re: Strange malloc()/free() behaviour
To: k3040e4 AT c210 DOT edvz DOT uni-linz DOT ac DOT at (Oberhumer Markus)
Date: Sat, 8 Jun 1996 13:39:00 -0600 (CDT)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <199606081356.PAA01331@c210.edvz.uni-linz.ac.at> from "Oberhumer Markus" at Jun 8, 96 03:56:05 pm
Content-Type: text
Content-Length: 485       

> When running this short program I get the following output:
> > Your system allowed me to malloc 15351808 bytes.
> > But now there's no free memory !

This is a flaw (feature?) in the default malloc() built into DJGPP.  It's
exceptionally inefficient in it's usage of memory, instead designed for
speed.  I have a somewhat slow but very memory efficient version which
I keep meaning to make public, but I just don't have the time.  There
are lots of other malloc packages out there.