User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9b2pre) Gecko/2007111400 Camino/2.0a1pre (like Firefox/3.0b2pre) Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en; rv:1.9b2pre) Gecko/2007111400 Camino/2.0a1pre (like Firefox/3.0b2pre) I get crashes with today’s trunk build when I click on flash objects that have been blocked. Tried different sites, happens everywhere. When I disable flash block, the page loads fine, including the flash object… I tried deleting pluginreg.dat – didn’t help. Also tried a completely new profile, only thing I changed before loading a page containing flash is to check the flash block setting. Reproducible: Always Steps to Reproduce: 1. enable flash block 2. go to a website containing flash content 3. click on the flash object placeholder Actual Results: browser crashes Expected Results: flash plugin should load and display formerly blocked content see two crash logs here: http://pastebin.mozilla.org/242506 http://pastebin.mozilla.org/242545

BTW: I wondered about the printing stuff in the crash log - haven’t printed anything for a long time. Flash player version: 9.0.98 (i.e. the current beta)

There's (presumably) no printing code on the stack, that just happens to be the closest unstripped symbol. I'm surprised by the lack of symbols in so many frames though if this is an official build. In the future, please attach crash logs as attachments; bugs last forever, and pastebin entries expire relatively quickly.

one of the crash logs added as an attachment :) (btw this is an official trunk build. no haxies or input managers installed)

I bet this is the same as bug 403757.

You think so? But I do not click anything on the adiumxtras site, it just crashes on load. I should probably also note that flash works without problems when flashblock is deactivated…

I don't see any Flash on adiumxtras. For whatever it's worth, I've seen a very long string of stripped symbols in official builds on trunk in crashes lately. cl

Oh, I meant to ask this before...did this just start happening with the 20071114 build, or did it happen with prior builds too? cl

(In reply to comment #7) > Oh, I meant to ask this before...did this just start happening with the > 20071114 build, or did it happen with prior builds too? A Camino 2007111302 (2.0a1pre) also crashes. But a home made build, checkout 20071112-15:30PDT, doesn't seem to crash. Will check that again next. With Minefield 2007111404 + FlashBlock latest http://crash-stats.mozilla.com/report/index/04caf017-9309-11dc-bd26-001a4bd43ef6?date=2007-11-14-23

The 2007111202 (2.0a1pre) does not crash FWIW, this is what I get with a home made build: Thread 0 Crashed: 0 <<00000000>> 0xf4000270 0 + -201325968 1 org.mozilla.camino 0x003014f4 PresShell::HandleEventInternal(nsEvent*, nsIView*, nsEventStatus*) + 496 2 org.mozilla.camino 0x00301948 PresShell::HandlePositionedEvent(nsIView*, nsIFrame*, nsGUIEvent*, nsEventStatus*) + 316 3 org.mozilla.camino 0x003037b4 PresShell::HandleEvent(nsIView*, nsGUIEvent*, nsEventStatus*) + 1036 4 org.mozilla.camino 0x00536550 nsViewManager::HandleEvent(nsView*, nsPoint, nsGUIEvent*, int) + 120 5 org.mozilla.camino 0x00538cbc nsViewManager::DispatchEvent(nsGUIEvent*, nsEventStatus*) + 1512 6 org.mozilla.camino 0x00532cc4 HandleEvent(nsGUIEvent*) + 76 7 org.mozilla.camino 0x0083f488 nsChildView::DispatchEvent(nsGUIEvent*, nsEventStatus&) + 184

Smaug, the line number/blame that Socorro picked out for philippe's crash in comment 8 is within your checkin for bug 401528: http://bonsai.mozilla.org/cvsblame.cgi?file=mozilla/content/events/src/nsEventStateManager.cpp&rev=1.720&mark=2382#2382 Based on that, I'm going to move this to Core:Event Handling (but not confirming, because people yell at me when I confirm Core bugs without reduced test cases ;) I can repro the crash, though.)

I was just going to suggest that myself.