On Mon, 6 Sep 1999, Richard Gaskin wrote:
> >> Does MC release temporary memory when it's done with it? I've had
> >> reports of one of our standalones not release memory (no externals in
> >> it). If this is not normal for MC I'll get more info together and
> >> generate a formal bug report.
> >
> >It does, but allocates in large blocks (32K in 2.2.X) and then breaks
> >them up into smaller pieces as needed. Only if all those pieces are
> >freed will the 32K block be freed, so depending on what exactly you're
> >doing, the total size reported by MacOS may only decrease slightly or
> >even not at all as you delete stacks or other things that use memory.
> >It just won't increase any more the next time you do something that
> >requires reusing that memory.
>
> I imagine it should be releasing this when it quits, yes?
According to Apple, this isn't supposed to be necessary. But we've
found that it may be, and so all memory is released when the engine
exits. We don't know of any memory leaks in 2.2.5.
Regards,
Scott
> - Richard Gaskin
> Fourth World
> Multimedia Design and Development for Mac, Windows, UNIX, and the Web
> _____________________________________________________________________
> [EMAIL PROTECTED] http://www.FourthWorld.com
> US: 800-288-5825 Int'l: 323-225-3717 Fax: 323-225-0716
>
>
********************************************************
Scott Raney [EMAIL PROTECTED] http://www.metacard.com
MetaCard: You know, there's an easier way to do that...
