Crash in <name omitted> | nsStyleContext::DoGetStyleVisibility<T>

NEW
Unassigned

Status

()

Core
Graphics: Layers
P3
critical
17 days ago
3 days ago

People

(Reporter: marcia, Unassigned, NeedInfo)

Tracking

({crash, regression, topcrash})

Trunk
Unspecified
Android
crash, regression, topcrash
Points:
---

Firefox Tracking Flags

(firefox60 affected)

Details

(Whiteboard: [gfx-noted], crash signature)

This bug was filed from the Socorro interface and is
report bp-deaaf888-3546-48fc-b250-dad4e0180206.
=============================================================

Seen while looking at nightly android crashes: http://bit.ly/2BZ3x8N. 116 crashes/89 installs. Crashes started using 20180204102100 

Possible regression range based on Build ID: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=92b6195a9367dec27fbf3efbe7824cf163aa017a&tochange=cac3a4e6000d7079f8cf0118a5c509b2527b3289

Top 10 frames of crashing thread:

0 libxul.so <name omitted> gfx/layers/ipc/CompositorBridgeChild.h:188
1 libxul.so nsStyleContext::DoGetStyleVisibility<true> obj-firefox/dist/include/nsStyleStructList.h:62
2 libxul.so FlushThrottledStyles layout/base/PresShell.cpp:6807
3 libxul.so nsDocument::EnumerateSubDocuments dom/base/nsDocument.cpp:8230
4 libxul.so FlushThrottledStyles layout/base/PresShell.cpp:6814
5 libxul.so nsDocument::EnumerateSubDocuments dom/base/nsDocument.cpp:8230
6 libxul.so FlushThrottledStyles layout/base/PresShell.cpp:6814
7 libxul.so mozilla::PresShell::HandleEvent layout/base/PresShell.cpp:7074
8 libxul.so mozilla::PresShell::HandleEvent layout/base/PresShell.cpp:7044
9 libxul.so nsViewManager::DispatchEvent view/nsViewManager.cpp:812

=============================================================
Should this go to PresShell instead?
Flags: needinfo?(jnicol)
This has moved up to the top browser crash in 60.
Keywords: topcrash
This crash seems to have been stopped in the 20180213100129 build, but I don't know what to attribute that to.
Priority: -- → P3
Whiteboard: [gfx-noted]
(In reply to Marcia Knous [:marcia - needinfo? me] from comment #3)
> This crash seems to have been stopped in the 20180213100129 build, but I
> don't know what to attribute that to.

And it came back in 20180218100125 build after being absent for several builds.
You need to log in before you can comment on or make changes to this bug.