🚀 go-pugleaf

> I am assuming that you have observed this when you stop your thread on a
> breakpoint and then checking 'About This Computer'.

Yes.

I used zoneranger like meeroh suggested, and it shows that only about
500 bytes are being used at the end of the heap (after starting a
thread), there's a HUGE section of free ram just before it.

Thanks for your help, both of you...

btw, Bell (Sympatico) sucks, it's not showing me your replies, I had to
go to google to see them.


Frank Pollard wrote:
> 
> It happens whenever I call yieldtoanythread, or yieldtothread. As soon
> as the thread starts, 'About This Computer' in the finder says the
> program has
> used all of its ram, even when I give it 150MBs and all the thread does is
> call printf.
> Message 2 in threadFrom: meeroh (macdev@meeroh.org)
> Subject: Re: threadmanager's using all my ram! 
> Newsgroups: comp.sys.mac.programmer.codewarrior, comp.sys.mac.programmer.help, codewarrior.mac
> Date: 2001-06-27 19:20:48 PST 
> 
> 
> 
> In article <3B3A636B.F4E0BD1F@macman.net>,
>  Frank Pollard <macman@macman.net> wrote:
> 
> >It happens whenever I call yieldtoanythread, or yieldtothread. As soon 
> >as the thread starts, 'About This Computer' in the finder says the 
> >program has used all of its ram, even when I give it 150MBs and all 
> >the thread does is call printf.
> 
> Have you tried using ZoneRanger and MacsBug to try to figure out why 
> that memory is being allocated and who is allocating it?
> 
> meeroh
> -- 
> To get random signatures put text files into a folder called "Random Signatures" into your Preferences folder.
> 
> 
> Post a follow-up to this message
> Message 3 in threadFrom: Tim Hosking (tim@trhosking.com)
> Subject: Re: threadmanager's using all my ram! 
> Newsgroups: comp.sys.mac.programmer.codewarrior, comp.sys.mac.programmer.help
> Date: 2001-06-28 07:12:09 PST 
> 
> 
> 
> in article 3B3A636B.F4E0BD1F@macman.net, Frank Pollard at macman@macman.net
> wrote on 27/6/01 6:51 pm:
> 
> > It happens whenever I call yieldtoanythread, or yieldtothread. As soon
> > as the thread starts, 'About This Computer' in the finder says the
> > program has
> > used all of its ram, even when I give it 150MBs and all the thread does is
> > call printf.
> 
> I am assuming that you have observed this when you stop your thread on a
> breakpoint and then checking 'About This Computer'.
> 
> If this is the case then has been posted here before and I don't recall
> anything ever being resolved. It does appear to be a quirk of the OS, and
> totally benign. I have dropped into MacsBug and checked my app's heap and
> there is always plenty of unused memory. It just seems that the Finder's
> about window is somehow getting it wrong.
> 
> Maybe someone at MetroWerks could check it out and provide a more accurate
> and therefore useful answer?