It's #2 top crasher in 10.0.2 and #5 in 11.0b5 on Mac OS X. Signature CrashInJS | JS_AbortIfWrongThread More Reports Search UUID b78a3636-981c-44a3-9c7f-588442120307 Date Processed 2012-03-07 17:06:45 Uptime 13 Last Crash 2.5 weeks before submission Install Age 2.4 days since version was first installed. Install Time 2012-03-05 07:01:50 Product Firefox Version 11.0 Build ID 20120228210006 Release Channel beta OS Mac OS X OS Version 10.6.8 10K549 Build Architecture x86 Build Architecture Info family 6 model 23 stepping 10 Crash Reason EXC_BAD_ACCESS / KERN_PROTECTION_FAILURE Crash Address 0x0 App Notes AdapterVendorID: 0x10de, AdapterDeviceID: 0x 863 EMCheckCompatibility True Frame Module Signature Source 0 XUL CrashInJS js/src/jsutil.cpp:95 1 XUL JS_AbortIfWrongThread js/src/jsapi.cpp:6317 2 XUL js_NewContext js/src/jscntxt.cpp:424 3 XUL XPCJSContextStack::GetSafeJSContext js/xpconnect/src/XPCThreadContext.cpp:241 4 XUL mozilla::plugins::parent::_getstringidentifier dom/plugins/base/nsNPAPIPlugin.cpp:1400 5 DivXBrowserPlugin DivXBrowserPlugin@0x484e 6 DivXBrowserPlugin DivXBrowserPlugin@0xa621a 7 DivXBrowserPlugin DivXBrowserPlugin@0x180b0 8 DivXBrowserPlugin DivXBrowserPlugin@0x89e5a 9 PlatformModule PlatformModule@0x6952 10 libSystem.B.dylib _pthread_start 11 libSystem.B.dylib thread_start More reports at: https://crash-stats.mozilla.com/report/list?product=Firefox&platform=mac&query_search=signature&query_type=contains&reason_type=contains&range_value=1&range_unit=weeks&hang_type=any&process_type=any&do_query=1&signature=CrashInJS%20|%20JS_AbortIfWrongThread

Yikes, we need to get them to fix their stuff ASAP. Kev, are you the guy to handle this sort of outreach?

Crashes are gone on Mac.

It's #7 top browser crasher in 13.0.1 and #8 in 14.0b8 on Mac. More reports at: https://crash-stats.mozilla.com/report/list?signature=nsXPConnect%3A%3AGetSafeJSContext

Ah, I was looking for JS_AbortIfOnWrongThread.

It's #26 top browser crasher on Mac OS X in 17.0 so no longer a top crasher.

Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.