This bug was filed from the Socorro interface and is report bp-3a46b447-c0f2-468b-b524-a20450180523. ============================================================= Top 10 frames of crashing thread: 0 xul.dll nsIContent::nsExtendedContentSlots::Traverse dom/base/FragmentOrElement.cpp:658 1 xul.dll mozilla::dom::FragmentOrElement::nsExtendedDOMSlots::Traverse dom/base/FragmentOrElement.cpp:783 2 xul.dll mozilla::FrameLayerBuilder::ComputeGeometryChangeForItem layout/painting/FrameLayerBuilder.cpp:4985 3 xul.dll mozilla::FrameLayerBuilder::WillEndTransaction layout/painting/FrameLayerBuilder.cpp:2213 4 xul.dll nsDisplayList::BuildLayers layout/painting/nsDisplayList.cpp:2614 5 xul.dll nsDisplayList::PaintRoot layout/painting/nsDisplayList.cpp:2779 6 xul.dll nsLayoutUtils::PaintFrame layout/base/nsLayoutUtils.cpp:3831 7 xul.dll mozilla::PresShell::Paint layout/base/PresShell.cpp:6312 8 xul.dll nsViewManager::ProcessPendingUpdatesPaint view/nsViewManager.cpp:480 9 xul.dll nsViewManager::ProcessPendingUpdatesForView view/nsViewManager.cpp:412 ============================================================= There is 1 crash in nightly 62 with buildid 20180522220730. In analyzing the backtrace, the regression may have been introduced by patch [1] to fix bug 1463116. [1] https://hg.mozilla.org/mozilla-central/rev?node=03487dd40d9b

I am not seeing any further crashes on 62 in the last 7 days.

Still no recent crashes. There is one from June 6 from 20180516032328, from 60.0.1. Should we close this bug?