In message <[EMAIL PROTECTED]>
Ralph Clark <[EMAIL PROTECTED]> wrote:
> I think I know now. Having monitored the Mozilla web site for quite a
> while I see that their often repeated rule-of-thumb definition of
> stability is that it stays up for one to two hours without crashing.
hehe. Probably good enough for Windows.
> Most recently, that was the requirement JWZ stated for the release of
> the current beta version. However they have used that definition before
> and I infer that the measure they'll use to define release quality for
> the final non-Beta version of Communicator will not too different.
> Moreover, experience of Netscape Communicator implies that a similar
> policy applies to commercial Netscape browsers.
>
> So my bet is that while Mozilla will be smaller, faster and a more
> accurate HTML renderer, it won't be any more stable.
I have hopes for the Gecko reimplementation. I also hope they'll allow one to
map in a natively installed JVM instead of their own. It's galling wanting to
use the JRun swing-based remote admin applet but not being able to, even
though Blackdown's JDK is perfectly capable of doing it with applications.
> The worst part of all this is when you've been editing a long email in
> Netscape Messenger's mail editor while browsing at the same time. Click
> on one link too many and bang! all Netscape windows close and hours of
> work are down the drain. Or the GUI locks up, all the Netscape windows
> stop refreshing and when in resigned desperation you issue a killall
> -HUP netscape, the whole X session reboots with a core dump.
Wow, I haven't had that happen! Netscape kept dying, but didn't take my
xsession down - unlike the KDE screensaver. Grr.
> (3) turn Java and Javascript off in Preferences if you are doing any
> browsing at all
They were off.
> (4) don't "mouse" the controls on any Netscape windows too much
> (5) keep an eye on memory usage using xosview or something similar
> (6) If you've had any part of Netscape Communicator running for more
> than an hour, close it all down and restart it before beginning your
> edit.
I was getting death after a few minutes. There was crud in files. I could
clear it by deleting a folder's .summary file, forcing it to re-create it,
but it would go wrong again later.
--
Rachel
http://www.enlarion.demon.co.uk/
--
To get out of this list, please send email to [EMAIL PROTECTED] with
this text in its body: unsubscribe suse-linux-e
Check out the SuSE-FAQ at http://www.suse.com/Support/Doku/FAQ/ and the
archive at http://www.suse.com/Mailinglists/suse-linux-e/index.html
