Meistersinger wrote:
What Operating system are you using? I have Firefox running in Mac OS X 10.8.5 as well as Windows 7 Ultimate 64-bit Service Pack 1.
I'm using Windows 8.
Meistersinger wrote:
Also, where did you download Firefox from? If it came from someplace other than mozilla.org or its mirrors, then you'll get all the garbage you're seeing. I got burned the same way.
Well, I thought it was Mozilla ... but I don't really remember, and so now I'm not so sure.
None of the crap was showing up to begin with because I was running NoScript... but it's been hellish ever since Firefox insisted on resetting - and thus shut off all of the extensions. NoScript must have been worked half to death from blocking all of that junk !
Meistersinger wrote:
Before you attempt to reinstall, you might want to run a registry cleaner to clean the junk out of the system registry. You also might run a full scan with a GOOD antivirus and malware package, like avast antivirus and Spybot Search and destroy (the only two security packages i trust for Windows)
Peretologic Regcure reckons that it found all manner of issues with the registry when I ran it, but fixing things up seems to have made not a lot of difference.
Chromium seems to be a bit less crashy than Firefox 24 was, but it's basically been doing the same thing... although thankfully, a bit less often.
I've been using AVG.
It seems to be pretty good.
Is there a reason I might want to be changing to use Avast Antivirus, instead ?
Cberg wrote:
What you have to remember about the Mozilla foundation is that crashes actually help them debug new versions. You're right that the competition usually has more security flaws, and this is why. No matter how unstable a given version of Firefox seems on your OS, Mozilla bug reporting is most likely the most reliable, and the foundation is motivated to fix individual users' problems as a result.
I would disagree with this, purely because the Mozilla crash report software has been failing to run when Firefox crashes on my system.
Without that functioning properly, they won't be receiving any information about when and why the browser is crashing... and consequently will probably be making no endeavours to remedy whatever my individual problem is.
So basically, Firefox 24 is so uselessly unstable on my PC that as a result, the Mozilla bug reporting software is hopelessly unreliable.
On the upside, it looks as though Chromium automatically recalls text put into posts such as this one, and reloads the text when restarting after a crash (no extension required).

which was good to find out.
I might give Firefox 25 beta a go next, hopefully this will work a bit better.