Closed Bug 1418300 Opened 7 years ago Closed 5 years ago

Crash in nsINode::GetParentObject

Categories

(Core :: DOM: Core & HTML, defect, P3)

x86
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox59 --- affected

People

(Reporter: baffclan, Unassigned)

Details

(Keywords: crash, nightly-community, regression)

Crash Data

This bug was filed from the Socorro interface and is
report bp-2633d36b-bfb3-4d34-9f03-847450171117,
       bp-a5fd38bc-c8c7-4542-b622-00aa30171117,
       bp-76e1a487-a51b-4ee0-bf3d-35a0a0171117,
       bp-7b273a51-db75-4f4f-b558-2ebf30171117.
=============================================================

Top 8 frames of crashing thread:

0 xul.dll nsINode::GetParentObject dom/base/nsIDocument.h:3971
1 xul.dll mozilla::dom::HTMLElementBinding::Wrap dom/bindings/HTMLElementBinding.cpp:8109
2 xul.dll mozilla::dom::HTMLElement::WrapNode dom/html/HTMLElement.cpp:42
3 xul.dll nsINode::WrapObject dom/base/nsINode.cpp:3027
4 xul.dll mozilla::dom::Element::WrapObject dom/base/Element.cpp:539
5 xul.dll mozilla::dom::HTMLCollectionBinding::DOMProxyHandler::get dom/bindings/HTMLCollectionBinding.cpp:534
6 xul.dll js::ProxyGetPropertyByValue js/src/proxy/Proxy.cpp:381
7  @0xad81b76643 

=============================================================


Application Basics: 
Name: Firefox
Version: 59.0a1
Build ID: 20171116220410
Update Channel: nightly
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0
OS: Windows_NT 10.0
The crash volume is really low, but would be good to at least understand what's up behind.
John, mind taking a first investigation for us here?
Flags: needinfo?(jdai)
Priority: -- → P3
Sure. I'll take a look. Keep NI for tracking.
Flags: needinfo?(jdai)
Component: DOM → DOM: Core & HTML

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Keywords: regression
You need to log in before you can comment on or make changes to this bug.