Open
Bug 1144813
Opened 9 years ago
Updated 1 year ago
crash in shutdownhang | mozilla::dom::CallbackObject::CallSetup::CallSetup(mozilla::dom::CallbackObject*, mozilla::ErrorResult&, mozilla::dom::CallbackObject::ExceptionHandling, JSCompartment*, bool)
Categories
(Core :: DOM: Core & HTML, defect)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox36 | ? | affected |
firefox37 | --- | unaffected |
People
(Reporter: u279076, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is report bp-3afd7eb5-ac63-413a-ae70-458252150311. ============================================================= 0 xul.dll mozilla::dom::CallbackObject::CallSetup::CallSetup(mozilla::dom::CallbackObject*, mozilla::ErrorResult&, mozilla::dom::CallbackObject::ExceptionHandling, JSCompartment*, bool) dom/bindings/CallbackObject.cpp 1 xul.dll mozilla::EventListenerManager::HandleEventInternal(nsPresContext*, mozilla::WidgetEvent*, nsIDOMEvent**, mozilla::dom::EventTarget*, nsEventStatus*) dom/events/EventListenerManager.cpp 2 xul.dll mozilla::EventTargetChainItem::HandleEventTargetChain(nsTArray<mozilla::EventTargetChainItem>&, mozilla::EventChainPostVisitor&, mozilla::EventDispatchingCallback*, mozilla::ELMCreationDetector&) dom/events/EventDispatcher.cpp 3 xul.dll mozilla::EventDispatcher::Dispatch(nsISupports*, nsPresContext*, mozilla::WidgetEvent*, nsIDOMEvent*, nsEventStatus*, mozilla::EventDispatchingCallback*, nsCOMArray<mozilla::dom::EventTarget>*) dom/events/EventDispatcher.cpp ============================================================= More reports: https://crash-stats.mozilla.com/report/list?product=Firefox&signature=shutdownhang+%7C+mozilla%3A%3Adom%3A%3ACallbackObject%3A%3ACallSetup%3A%3ACallSetup%28mozilla%3A%3Adom%3A%3ACallbackObject%2A%2C+mozilla%3A%3AErrorResult%26%2C+mozilla%3A%3Adom%3A%3ACallbackObject%3A%3AExceptionHandling%2C+JSCompartment%2A%2C+bool%29 Volume: * 646 reports in the last week (1.05% of all DOM crashes) Platform Breakdown: * 61% on Windows 7 with 35% on other versions of Windows * 3% on Mac OS X * 0% on Linux Product Breakdown: * All crashes are on various Firefox 36 versions with 98% on 36.0.1 * No crashes with Firefox 37 or later Correlations: * No correlations exist Top URLs: * facebook.com * about: pages * yahoo.com * google.com * cnn.com Comments: There seems to be a variety of comments which mention seeing the crash reporter at various stages; either resuming from sleep, soon after closing Firefox, or soon after starting Firefox and browsing (mainly on Facebook).
[Tracking Requested - why for this release]: nominating to track since these crashes are only appearing against Firefox 36 at this point (nothing for previous or following versions).
tracking-firefox36:
--- → ?
Updated•9 years ago
|
Crash Signature: [@ shutdownhang | mozilla::dom::CallbackObject::CallSetup::CallSetup(mozilla::dom::CallbackObject*, mozilla::ErrorResult&, mozilla::dom::CallbackObject::ExceptionHandling, JSCompartment*, bool)] → [@ shutdownhang | mozilla::dom::CallbackObject::CallSetup::CallSetup(mozilla::dom::CallbackObject*, mozilla::ErrorResult&, mozilla::dom::CallbackObject::ExceptionHandling, JSCompartment*, bool)]
[@ shutdownhang | mozilla::dom::CallbackObject::CallSetup::…
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
Updated•2 years ago
|
Severity: critical → S2
Comment 2•2 years ago
|
||
Since the crash volume is low (less than 5 per week), the severity is downgraded to S3
. Feel free to change it back if you think the bug is still critical.
For more information, please visit auto_nag documentation.
Severity: S2 → S3
Updated•1 year ago
|
Crash Signature: [@ shutdownhang | mozilla::dom::CallbackObject::CallSetup::CallSetup(mozilla::dom::CallbackObject*, mozilla::ErrorResult&, mozilla::dom::CallbackObject::ExceptionHandling, JSCompartment*, bool)]
[@ shutdownhang | mozilla::dom::CallbackObject::CallSetup::… → [@ shutdownhang | mozilla::dom::CallbackObject::CallSetup::CallSetup]
[@ shutdownhang | mozilla::dom::CallbackObject::CallSetup::CallSetup]
You need to log in
before you can comment on or make changes to this bug.
Description
•