Firefox crashes?
June 12th 2008 08:20
I don’t know whether it’s something to do with the imminent arrival of Firefox 3, but Firefox 2 has been playing up something awful. I’ve never known Firefox in any version to crash at all, but recently, both at work and at home, it’s been crashing constantly. Maybe Firefox 2 is upset at the fact that it’s about to be replaced?
I wrote about the Guinness World Record Firefox is attempting a few posts back – the day for this is much closer now: June 17th. NZ’s number of pledges has now overtaken Ireland’s: 3649 compared to 3519. Back on the 30th May, New Zealand only had 824. China, on the other hand, has gone from 5,562 to 16,657 in that time.
Getting back to the crashing, I checked out what Firefox themselves have to say about this. There’s a good page here, but of course, while Firefox is running – as it is at the moment – I don’t feel inclined to fiddle about with it. It’s a bit like a car; as long as it’s going, we don’t want to get under the hood in case we find something we’d prefer not to!
The other thing is that I’m disinclined to tinker with my computer; while my son the geek can get anything working by racing over the keys at a rate of knots, I get jiggered by the techno-language, and prefer to maintain a hands-off approach wherever possible.
And then there’s the problem with the way things are said: For most users, Firefox doesn't use an abnormally large amount of computer memory. For others, however, Firefox's memory consumption is a major problem.
And that means what? Am I one of the favoured many or the favoured few? I just keep typing and hope everything holds together.
I wrote about the Guinness World Record Firefox is attempting a few posts back – the day for this is much closer now: June 17th. NZ’s number of pledges has now overtaken Ireland’s: 3649 compared to 3519. Back on the 30th May, New Zealand only had 824. China, on the other hand, has gone from 5,562 to 16,657 in that time.
Getting back to the crashing, I checked out what Firefox themselves have to say about this. There’s a good page here, but of course, while Firefox is running – as it is at the moment – I don’t feel inclined to fiddle about with it. It’s a bit like a car; as long as it’s going, we don’t want to get under the hood in case we find something we’d prefer not to!
The other thing is that I’m disinclined to tinker with my computer; while my son the geek can get anything working by racing over the keys at a rate of knots, I get jiggered by the techno-language, and prefer to maintain a hands-off approach wherever possible.
And then there’s the problem with the way things are said: For most users, Firefox doesn't use an abnormally large amount of computer memory. For others, however, Firefox's memory consumption is a major problem.
And that means what? Am I one of the favoured many or the favoured few? I just keep typing and hope everything holds together.
| 65 |
| Vote |
Shared on
Subscribe to this blog
















Comment by Anonymous
And even the FF's interface is (slightly) different than ever before: now with only one page open (or even none) it displays it in the single tab - it used to be that if you are using only one page at the moment the tab interface is suppressed and that single page is displayed in the whole content window.
I will try to completely uninstall FF and install it afresh, to see if any of the other extensions is misbehaving. If that does not work, I will check if the previous version of FF behaves better.
Comment by Mike Crowl
Webitz
Work Report
Comment by Anonymous
Today (a day later) it seems to have stabilized. I'm not too sure yet, because my PC and FF runs OK thus far (already for about 12 minutes).
Comment by Mike Crowl
Webitz
Work Report