Xref: utzoo comp.windows.ms.programmer:2351 comp.windows.ms:12472 comp.os.msdos.misc:2023
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!dali.cs.montana.edu!milton!sumax!amc-gw!nwnexus!keithp
From: keithp@nwnexus.WA.COM (Keith Pleas)
Newsgroups: comp.windows.ms.programmer,comp.windows.ms,comp.os.msdos.misc
Subject: Re: Out of Resources in Windows3? [Summary, long]
Summary: Try HEAPWALKER in SDK
Message-ID: <503@nwnexus.WA.COM>
Date: 9 May 91 05:52:05 GMT
References: <1991May6.075011.14338@amd.com>
Reply-To: keithp@nwnexus.UUCP (Keith Pleas)
Organization: Northwest Nexus Inc.; Seattle, WA
Lines: 16

In article <1991May6.075011.14338@amd.com> indra@brahms.amd.com (Indra Singhal) writes:
>Note: the only
>tool that measures this, is Progman/Help/About and the accuracy is
>rounded to the nearest digit with no real units just %. [Any takers for
>a better tool?]

Well, the HEAPWALKER utility that comes with the MS Windows SDK will let
you explore this in greater detail.  FWIW, my understanding is that
Systems Resources is equal to the 64K segment set aside for the global
heap.  I also understand that this relatively small limit will be greatly
increased with Windows 3.1.  I looked into a specific situation where
system resources seemded to disappear when Shelling out to a TPW generated
program from WFW.  I found that the application destroyed itself, but left
some heap memory unrecovered in the User segment.  Also, I am running ATM,
which will increase in size to accomodate additional fonts; some of this
memory is not reclaimed when the application terminates.