Or, at a minimum, does FF3.5 deal with and/or prevent crashing any better?????

IMO, that is a much more important feature than this eye candy and GUI nicety stuff. FF3.0 is great but it still crashes way the hell too often. And for an app that I spend MOST of my day using, ONE crash per WEEK is way the hell too often.

The memory issue is the second one, a clean FF (even one with the scriptblocker plugin which should prevent heavy flash and java applets and browser apps and ads load) uses way to much memory. If I need a low demand environment I use Opera or Seamonkey.

Seamonkey does this for me. Last time I checked, Firefox doesn’t. If I have a home page group of 15 different tabs in Firefox, and I click [Home], I wind up with 29 tabs in my browser, and an essentially dead browser because my workstation doesn’t have the horsepower to run 29 tabs. (God help me if I click [Home] twice.)

Why is that?? Is there some kind of history to this?

I have tried the latest FF 3.0.8 on Mythdora 5 and FF 3.0.9 on win xp.

On Mythdora until 3.0.8 every 3.x version of FF would crash every second time Ie press the back button. Thankfully now with 3.0.8 it doesn’t crash at all. I think general stability fixes are the most important. At the same time the average homer user and the commercial world both demand new flashy features. I think a balance has to be struck.

I really think it’s more stable on Win xp than linux.

So yes, the private browsing is a great feature, and the others except geolocation has me freaking out. Could you please provide a link for how u disable it?

Also, I think FF is still the best browser. It provides the interface many prefer like myself. And the privacy features are a reason I use only FF pretty much for any encrypted browsing, and now for everything else. I really have a soft spot for FF.

But I think that 3.5.1 could be the real game changer in terms of stability.

thanks

wasim

I restarted both FF and Chrome (both cached, so it’s
a ‘load-from-cache’ measurement) and measured the baseline resource
consumption and then loaded them with the same 20 pages (including a
number that are lousy with ads, extraneous JS, etc).

Starting up and pointing to news.google.com, firefox (1 process) takes
4s to start and load the page, and takes up 230MB (V) & 83MB (R).

Chrome takes ~1.5s (2 processes) and takes up a total of 199MB(V) and
48MB(R).

* Advantage chrome.

Note that chrome starts an initial instance and then each tab as a
separate process which reduces the probability that a fatal error in
one will take down the rest (and it seems to be working based on my
experience).

* Advantage chrome.

However, for the 20 pages loaded, firefox (as a single process) uses
about 1/3 the RAM (584MN (R) for firefox and a total of 1772MB (R)
for chrome (21 processes)) and 2/3 of the CPU cycles as well (19.2%
vs 28.9%). While I didn’t measure the load time of each page, it
seemed that FF loaded them faster, especially towards the end of the
list of pages.

* Advantage firefox.

While chrome is VERY stable, it’s still quite incomplete (no printing,
no youtube, few plugins, some interface glitches. however, based on
this preview, I’m very impressed. If they can cut down on resource
use (probable), maintain speed and stability (probable), and
encourage the same kind of plugin and user community as FF (hmmmm),
it’s certainly a contender.