🚀 go-pugleaf

   ----- Transcript of session follows -----
554 POST-MACAPP-BETA-3... Recipient names must be specified

   ----- Unsent message follows -----
Received: by alink-gw.apple.com (5.65/27-Sep-1991-eef)
	id AA11336; Sun, 13 Dec 92 12:11:47 -0800
	for 
Date: 12 Dec 92 23:28 GMT
From: Gateway@AppleLink.Apple.COM (to Internet/BITNET/UUCP)
Subject: Re: Memory Leaks
To: MACAPP3TECH$@AppleLink.Apple.COM (MacApp 3 Technical Discussion)
Message-Id: <9212131953.AA24329@apple.com>
X-Original-Document-Id: <9212131953.AA24329@apple.com>

From:
References: , ,, <724192662.2890464@AppleLink.Apple.COM>
Organization: (Evil Eye Creature from Mars, Inc.)
Sender: macapp.admin@applelink.apple.com
To: MacApp3Tech$@Applelink.apple.com
 
In article <724192662.2890464@AppleLink.Apple.COM>,
DEWAELE.W@AppleLink.Apple.COM (De Waele Willy - Gent,BE,IHD) wrote:
>
> Hi Peter,
>
> On the Developer CD's, there is *somewhere* a 'dcmd' 'Leaks' which should be
> copied/pasted into the 'Debugger Prefs' of MacsBug.
> I didn't have time/occasion to experiment with this.
 
The Swatch application is also handy for finding about leaky apps, just let
it
run in a window, and check out if the free heap numbers are mysteriously
ticking down even if you are not doing anything.  Even better, if you could
figure out the size of the chunks that decrease, it might even give an
indication what is really leaking (sometimes).
 
Kent
-------------------
Kent Sandvik (UUCP: ....!apple!ksand; INTERNET: ksand@apple.com)
DISCLAIMER: Private activities on the Net.