Shiretoko (mac os x 20081211) always crashes on http://quicksilver.en.softonic.com/mac , the download page for the popular Quicksilver mac app launcher.

Can you please give more info? Steps to repro, what we need to do at that page to make a crash, new profile, etc. A stacktrace would also be nice. http://new.quality.mozilla.org/bug-writing-guidelines. What build are you using?

Sorry for that, I was trying to narrow down the issue and I caught it. It's caused by Adblock Plus 1.0 add-on. It's said to be compatible with Shiretoko but it makes it always crash on that page. relevant crash reports: 2848ed48-2c12-4993-b73e-d02ef2081211 12/11/08 11:05 PM d84e1e08-5401-46a7-a6bb-d4b072081211 12/11/08 10:39 PM build: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20081211 Shiretoko/3.1b3pre Just browse the URL given with Adblock+1.0 installed. There's no other step to repro. Does not crash if no extension in the profile. Always crash with AdblockPlus 1.0 installed.

If I was not clear enough, there is nothing to do IN the page because you don't reach the page at all... The browser crashes even before anything is displayed.

OK, if it crashes with ABP, then it is a problem with that extensions, and should be reported to them.

bp-2848ed48-2c12-4993-b73e-d02ef2081211 bp-d84e1e08-5401-46a7-a6bb-d4b072081211

BTW, I can't confirm on Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.0.4) Gecko/2008102920 Firefox/3.0.4. or trunk. and I have ABP.

Could be mac only.

mail sent to Wladimir Palant, adblock+'s author

I don't crash at http://quicksilver.en.softonic.com/mac in today's Shiretoko or Minefield nightlies. I don't have any extensions installed. I tested on OS X 10.5.5.

(In reply to comment #9) Comment #2 said you have to have ABP, which causes this. Making it INVALID.

Tyler: An extension that doesn't contain binary components can not crash Gecko and it's Geckos fault. A hang/freeze can of course be a bug in the extension

(In reply to comment #10) > (In reply to comment #9) > Comment #2 said you have to have ABP, which causes this. Making it INVALID. Tyler, did you look at the stack trace ? ABP is chrome only and lines of JS, even complex and powerful, should not crash the JS engine. There could be bad JS on ABP's side, but a crasher is not a normal behaviour for a rendering engine and that is Gecko's fault. Mathias, thanks for fixing that while old europe was asleep.