Path: utzoo!attcan!uunet!lll-winken!lll-lcc!ames!haven!umd5!jonnyg
From: jonnyg@umd5.umd.edu (Jon Greenblatt)
Newsgroups: comp.windows.ms
Subject: Re: Mem eating
Keywords: disgard free memory
Message-ID: <4441@umd5.umd.edu>
Date: 14 Jan 89 19:49:12 GMT
References: <33587@grapevine.uucp>
Reply-To: jonnyg@umd5.umd.edu (Jon Greenblatt)
Organization: University of Maryland, College Park
Lines: 18

In article <33587@grapevine.uucp> parker@grapevine.uucp (Parker Waechter) writes:
>An aplication I am writing seems to be holding 20K or so after the program 
>terminates (as checked by command window aboutbox).  I was careful about 
>dealocating my pens and brushes, and the big blocks of memory are done with 
>
>parker@sun.com

	I think the problem is with MS WINDOWS brain dead memory management.
Memory is allocated from the global heap instead of a local processheap there
causing a great deal of interprocess fragmentation. The about box
in the command window is showing you the largest available block of memory,
not the amount of memory available. Use heap walker to confim that the
problem is in the heap structure. From my experience you don't have to
close windows or destroy objects when terminating a process, its done for
you. Please do not depend on brushes and windows going away automagicaly
though, I'm sure the manual says to do it for a reason.

					JonnyG.