There is no memory leak in IE 5, and I believe Jimmy Grewal. The Mac OS provides APIs and using free memory is legit. Quiting the app and not freeing memory is. But often, background processes, even an AppleScript, will not be released and fraqment memory.
Get rid of all those inits that get loaded in memory.
On servers it is common practice on WindowsNT/2000 to have to reboot. it is a common problem.
==================
>> From: Jimmy Grewal <
[email protected]>
>> Newsgroups: microsoft.public.inetexplorer.mac
>> Date: Wed, 29 Mar 2000 09:41:49 -0800
>> Subject: Re: Memory leak in IE 5?
>>
>> There are no memory leaks in the product (we use several tools to check for
>> memory leaks while loading hundreds of web pages).
>>
>> What you are seeing is our attempts to compensate for the lack of a modern
>> memory management system in MacOS 8/9. We use a normal system call to ask
>> for unused system heap when the app needs more memory.
>>
>> If you see that IE is using 14.6mb while viewing a particular page, that
>> doesn't mean that all of that memory is required for that page. That number
>> slowly grows as we load more and more pages and need more memory to load
>> certain elements...they only way for us to return memory is to quit the
>> application at which point that memory is then available to other programs
>> of the MacOS. If we didn't do it that way, you'd have to set the
>> application partition to the largest possible number the app would ever
>> need...not the ideal scenario for casual web surfers on 32mb machines.
>>
>> We can stop doing all this stuff under MacOS X and I can't wait.
>>
>> -Jimmy
>>
------------------------
> From: "John W. Baxter" <
[email protected]>
> Newsgroups: microsoft.public.inetexplorer.mac
> Date: Fri, 31 Mar 2000 14:17:39 -0800
> Subject: Re: Memory leak in IE 5?
>
> Just to make things more fun, there are three heaps involved:
>
> The application heap (within the space whose size is determined using
> the informatino seen in the Memory pane of Get Info in Finder. (I say
> that carefully because various system versions add various small
> amounts.)
>
> System heap. Heap space used by the system, and for certain
> application-specific things ("system" handlers for Apple events, for
> example).
>
> Process manager heap. The memory from which is allocated the space for
> each application heap. AND the space from which is allocated "Temporary
> Memory".
>
> Most references I see to system heap in news postings are really
> referring to the process manager heap.
>
> --John
=========================
If $100 buys 128MB RAM today, and ten yrs ago u'd be lucky to buy 2MB for that price - buy some! 10MB is just not worth losing sleep over. If you want to run today's apps, and they run better with 32MB (system, browser, etc). If that is too rich there is always iCab or an alternative.
"Mac OS __ eats/uses/takes too much" etc. and there are memory leaks.." so what? Go run Linux or wait a couple months. By next year we'll be running X.II or something.
Apple provides tools, and if developers use the tools, do the best they can, or maybe the tools are faulty or other problems in the OS. Unix has been around for what? 20+ yrs industrial strength OS.
Gregory
Top