After updating to vr. 3.6.17 Firefox starts grabbing memory, cpu goes to 100%, and it crashes w/o a crash report, 2-3 times a day
OS Win2K sp4 AMD Atholn x2
Firefox announces it cannot provide a crash report on the crash
All Replies (5)
I have similar problem only using XPPro/SP3. Once open even if just sitting unused it continues to gobble memory and crashes. It crashed a couple of times a day since the update, has locked the system up a couple of times and crashed a total of 14 times today, the last three while trying to send crash reports. All since the 3.6.17 update. It has become unusable (I'm posting this from Opera 11). From scanning the forum looks like Apple folks are having similar problems with the last update as well.
If I was of a paranoid turn of mind I'd think it was a way to get people to move to FF4.
NyteOwl trɔe
Yes, my puter crashes at least once an hour, with no crash report. This has happened since I upgraded to 3.6.17 (I HATE 4) and now ALL MY SAVED PASSWORDS ARE GONE !!!!! HOW CAN I RETRIEVE ? THIS IS A DISASTER !!!
Sorry to hear about the passwords. I can't help there I'm afraid as it is not a feature I've ever used. I use an external secured password manager.
So far FF has crashed 6 times in the last 3 hours. A bit better than yesterday's record but still unacceptable.
If this continues I'm afraid I'll be forced to find another browser which is unfortunate as I've always liked the Mozilla/FF feature set and extensibility.
Hi NyteOwl, i went back to FF 3.6.16 and NO MORE CRASHES !! also no passwords but I am dealing with that...I also use a secure manager so at least I am not TOTALLY screwed !!!
Now, one thing I didn't mention is that I had probably around 100+ tabs open, but the memory used was about half my total on that machine, so... no big deal, right?
But I took the plunge to 4.0.x tonight, we'll see as I ramp things up to 'rediculous' tabs over the next couple of days. I might actually try to put on Flash as a while back it was causing too many problems as well, so *wack* it was gone. So, we'll see.