On Mon, 06 Mar 2000, Nils Jeppe wrote:
On Mon, 6 Mar 2000, Curtis Maloney wrote:
Until now, I've been using Netscape, whilst desperately searching for some replacement that didn't haemorhage memory. I think I've even managed to narrow down which part of NS is losing the memory (it's the edit box, which is why it seems to happen quicker when working with ZOPE).
NS (4.72) goes up to I guess 40 MB or so in worst case here. Just restart it every day and it should be fine. Also, RAM is cheap (ok not as cheap as it used to be a year ago, but anyway), so make sure you have 128 MB of ram or more in your machine.
Yesterday I had to restart NS no fewer than 5 times, to prevent the 'swap-to-death' situation. I have 96M in my machine, and i've been careful to eliminate all extraneous tasks to reduce memory usage. Yes, memory is cheap, but to get this box to 96M (from the original 32) took quite some wrangling, since it seems ordering more RAM here can have at least an 8 day lead time, amongst other things. As a programmer myself (ZOPE is like a holiday :) I know that memory leaks can be easy to code, and tiresome to track. But in an application as large as Netscape, I would hope for slightly tighter quality controls, and a little more coding discipline. There are some fairly simple guidelines you can follow to write "zero resource loss" programs. </rant>
However, in my searches I've yet to find ANYTHING under Linux that comes close to the functionality of NS.
Mozilla is way cool, but it's still alpha so use at your own risk. I found it is almost, but not quite, ready for real use.
Yes, I looked into Mozilla yesterday. However, I discovered it will ONLY work with the GTK library. Now, whilst I have nothing against the GTK lib, I also don't have ANY other apps using it. Oh well... -- Have a better one, Curtis. <dtml-var standard_work_disclaimer>