canavan wrote:
I haven't seen any glitches.
Could be my 2@ graphics situation ...
Ran 'er hard for a few days and put 'er away wet, here's what it looks like to me :
Removed Firefox 2 this morning as having two versions of Firefox installed makes nothing but trouble. Yes, it's possible, but it doesn't work well.
FF3 functions better as a browser but it is a little less stable. With what I've been doing it crashes more frequently but at least the crashes are more predictable, and the chances of getting the problem fixed are higher.
If you run it on sites like Nekochan, which are mostly text and a few photos and standard html, it's great.
If you find yourself on more commercial sites with a lot of javascript, spyware, horseshit advertising gimmicks and track-you scripts, it will go down if you have very many tabs open. Four open tabs seems to be okay, except on really crappy sites.
I seem to get two kinds of crashes - the good ol' unexplained
Code:
Select all
moz_run_program[36]: 1868 Memory fault
and
Code:
Select all
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
It seems like about 50-50. At least the 'std::bad_alloc' gives a clue to what it is. If this cause goes away in the future we should cut our crashes in half. Yea !
At hi-res, it's
waaaay
better. At lower res on older, slower hardware Flop2 might be a better choice. I'm not sure how well this would run on an Indigo2 or an O2. If you have the faster hardware, it's worth upgrading.
One small step for man, one giant leap for mankind