From:	mdruiter AT cs DOT vu DOT nl
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Exacltly when does actually DJGPP free allocated memory?
Date:	Thu, 1 Jul 1999 14:06:21 GMT
Organization:	Fac. Wiskunde & Informatica, VU, Amsterdam
Lines:	17
Message-ID:	<7lfskt$np1@cs.vu.nl>
References:	<7lfo40$jlu$1 AT news1 DOT kornet DOT net>
NNTP-Posting-Host:	sloep108.cs.vu.nl
X-Sender:	mdruiter AT cs DOT vu DOT nl
User-Agent:	tin/pre-1.4-19990413 ("Endemoniada") (UNIX) (SunOS/5.5.1 (sun4u))
X-Poster-Key:	sha1:N/iyy1DFp8+Ql3oLRTSGfAI8KHs=
Cancel-Lock:	sha1:XcDCzsELqZDO2l2QjD+CG5+GZJI=
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Seunghwan Ji <shjee AT nexgen DOT co DOT kr> wrote:
> Exaclty when does actually DJGPP(or allegro) free allocated memory
> after free()? Is it after some minutes? Is it after special function
> calls? or Only after the program ends(exit to DOS)..?

IIRC, free'd blocks are marked as available for use by following calls
to malloc. They are *not* returned to DOS (or memory would become very
fragmented!). Normally, memory usage should stabilize after a while,
because most free'd blocks will be malloc'ed again.

Hope this helps.

-- 
*Groeten, Michel*.      _http://www.cs.vu.nl/~mdruiter_
   ____________ 
   \  /====\  /         "You know, Beavis, you need things that suck,
    \/      \/           to have things that are cool", Butt-Head.

- Raw text -