Closed Bug 1457414 Opened 7 years ago Closed 7 years ago

Crash in nsStubMutationObserver::AttributeWillChange

Categories

(Core :: XUL, defect)

Unspecified
macOS
defect
Not set
critical

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr52 --- unaffected
firefox59 --- unaffected
firefox60 --- unaffected
firefox61 --- affected

People

(Reporter: calixte, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash, regression)

Crash Data

This bug was filed from the Socorro interface and is report bp-3568e654-c15d-4795-8842-492be0180427. ============================================================= Top 10 frames of crashing thread: 0 XUL nsStubMutationObserver::AttributeWillChange dom/base/nsStubMutationObserver.cpp:17 1 XUL nsNodeUtils::AttributeWillChange dom/base/nsNodeUtils.cpp:157 2 XUL mozilla::dom::Element::SetAttr dom/base/Element.cpp:2517 3 XUL nsScrollbarFrame::UpdateChildrenAttributeValue dom/base/Element.h:839 4 XUL nsScrollbarFrame::AttributeChanged layout/xul/nsScrollbarFrame.cpp:99 5 XUL mozilla::RestyleManager::AttributeChanged layout/base/RestyleManager.cpp:3324 6 XUL mozilla::PresShell::AttributeChanged layout/base/PresShell.cpp:4458 7 XUL nsNodeUtils::AttributeChanged dom/base/nsNodeUtils.cpp:170 8 XUL mozilla::dom::Element::SetAttrAndNotify dom/base/Element.cpp:2711 9 XUL mozilla::dom::Element::SetAttr dom/base/Element.cpp:2537 ============================================================= There is 1 crash in nightly 61 with buildid 20180426220144. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1431246. [1] https://hg.mozilla.org/mozilla-central/rev?node=d3b5dfca6a90
Flags: needinfo?(timdream)
Without an STR this is not really actionable. I would like to wait and see if this shows up more and hopefully find a test case to make this actionable.
There hasn't been another report since this was filed. Resolving as WFM.
Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(timdream)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.