Nicholas Clark wrote:
Dear firefuckwit developers - prepare to meet an ice pick...
Apparently lots of threads have this subject line. Hmmm. Why could that be?
I was just about to start a thread with this same name. You see, on my
workstation, about once a day on average the fox burns out and dumps core.
Apparently there are at least two failure modes:
* I go to a site which has Flash contents (usually following a link someone sent
in a mail message). I'm not sure it's Flash; maybe it's other not-plain-HTML stuff.
* I do nothing. That's right, I go away from my machine and when I come back,
the frisky fox has already taken a dump. Maybe it doesn't want to live in the
same universe with xlock.
At least the first failure mode happens both with Mozilla (some version from the
very beginning of the century) and the latest and greatest Firefox (the cunning
thing updates itself automatically and has the NERVE to happily tell me about it
after each crash).
Now, I could blaim plug-ins for viewing the not-plain-HTML contents, but
wouldn't it be better if *Firefox* blaimed them (by, say, looking at it's call
stack right before it's death) and asked me if I wanted to uninstall them or
something? Seems feasible to me. And then there are the crashes caused by not
doing anything.
