forwarded 362874 https://bugzilla.mozilla.org/show_bug.cgi?id=311172 tag 362874 fixed-upstream thanks
On Sun, Apr 16, 2006 at 01:01:51AM -0700, Russ Allbery <[EMAIL PROTECTED]> wrote: > Mike Hommey <[EMAIL PROTECTED]> writes: > > > Your problem is that the extensions WAS properly disabled. But your > > userContent.css file still contained a reference to it. Now the question > > is, what the hell does this do in your userContent.css ? > > Not a clue. > > > Did you add it yourself ? > > No. > > > Did the extension add it itself ? > > I would assume so, since I definitely didn't do it myself. > > > If it is the latter, then there's a serious issue with flashblocker. It > > shouldn't touch anything like this. > > > So the real crash bug seems to be that if you bind some inexisting stuff > > to an element, firefox crashes. I must say I'm not surprised. Firefox is > > full of shi^H^Htuff like this. > > I discovered this by poking through .mozilla/firefox and was retrying the > page each time I changed something. Since this worked with a new user > account, the first thing I decided to try cleaning out was extensions. > Deleting the disabled extension out of extensions/ didn't help, nor did > removing it from Extensions.rdf (although I'm not sure if that's even > used), but as soon as I deleted userContent.css, the page loaded without > any trouble at all. > > I see that it does have Flash on it, which makes me wonder if the > instability I've been seeing is related to the growing number of Flash > "banner" ads and this bug triggering on them. Okay, I found the upstream bug, it should be fixed in firefox 1.5.0.4. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
