Path: utzoo!attcan!uunet!snorkelwacker!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: Swelling Server Problem
Message-ID: <9009201358.AA02155@expire.lcs.mit.edu>
Date: 20 Sep 90 13:58:27 GMT
References: <59567@bbn.BBN.COM>
Sender: root@athena.mit.edu (Wizard A. Root)
Organization: The Internet
Lines: 17

This is nearly approaching another frequently asked question.
"grows enormously" gives me an idea that it's big, but you've
given absolutely no idea what your application does, or how much
"enormous" is, so what's there to say?  Similarly "never shrinks
back down" doesn't indicate whether you mean process size or resident
set size.  I'll assume process size.  In that case, please think about
what your vendor's system does.  Try an experiment, compile and run this
simple program:

main()
{
    free(malloc(8000000));
    pause();
}

See if the process size ever goes down.  If it doesn't, why would you
expect the server's process size to go down?