Closed Bug 1679733 Opened 5 years ago Closed 1 year ago

Crash in [@ nsLayoutUtils::HasAnimationOfPropertySet]

Categories

(Core :: Graphics, defect, P3)

Unspecified
Windows 10
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr78 --- affected
firefox85 --- affected
firefox86 --- affected
firefox87 --- affected

People

(Reporter: gsvelto, Unassigned)

References

Details

(Keywords: crash, Whiteboard: [not-a-fission-bug])

Crash Data

Maybe Fission related. (DOMFissionEnabled=1)

Crash report: https://crash-stats.mozilla.org/report/index/6679f10a-4171-4be8-aff7-9bdfc0201127

Reason: EXCEPTION_STACK_OVERFLOW

Top 10 frames of crashing thread:

0 xul.dll static nsLayoutUtils::HasAnimationOfPropertySet layout/base/nsLayoutUtils.cpp:240
1 xul.dll static nsLayoutUtils::HasAnimationOfTransformAndMotionPath layout/base/nsLayoutUtils.cpp:280
2 xul.dll nsIFrame::HasPerspective const layout/generic/nsIFrame.cpp:1825
3 xul.dll nsDisplayTransform::GetLayerState layout/painting/nsDisplayList.cpp:8224
4 xul.dll RequiredLayerStateForChildren layout/painting/nsDisplayList.cpp:5634
5 xul.dll nsDisplayTransform::GetLayerState layout/painting/nsDisplayList.cpp:8239
6 xul.dll RequiredLayerStateForChildren layout/painting/nsDisplayList.cpp:5634
7 xul.dll nsDisplayTransform::GetLayerState layout/painting/nsDisplayList.cpp:8239
8 xul.dll RequiredLayerStateForChildren layout/painting/nsDisplayList.cpp:5634
9 xul.dll nsDisplayTransform::GetLayerState layout/painting/nsDisplayList.cpp:8239

This appears to be a stack overflow while building display lists. It started on nightly so disregard the crashes that aren't on nightly because they are unrelated. Users have reported that the crash is often rejected by our crash machinery because it's too large (10+ MiB) so the volume here might as well be larger.

Will, I've been sent a few crash reports that users were unable to submit. The minidump was ~14 MiB in size, I vaguely remember that we bumped up the maximum size of the crash reports that Socorro accepts so I was a bit puzzled that this was rejected. Maybe we didn't increase the size enough? This crash is a stack overflow so it's rather important that it can be reported correctly.

Flags: needinfo?(willkg)
Flags: needinfo?(cpeterson)
Severity: -- → S4
Priority: -- → P3

Gabriele: We did increase the max payload size to 25mb (bug #1648387). Maybe the 14mb minidump + whatever else is in the payload exceeds our max size. I created bug #1679787 to increase it again.

Flags: needinfo?(willkg)

(In reply to Gabriele Svelto [:gsvelto] from comment #0)

Maybe Fission related. (DOMFissionEnabled=1)

I don't think this crash is Fission related, even though one of the (two) 85.0a1 crash reports had Fission enabled.

Flags: needinfo?(cpeterson)
See Also: → 1679545

(In reply to Chris Peterson [:cpeterson] from comment #3)

(In reply to Gabriele Svelto [:gsvelto] from comment #0)

Maybe Fission related. (DOMFissionEnabled=1)

I don't think this crash is Fission related, even though one of the (two) 85.0a1 crash reports had Fission enabled.

Crash volume is very low and we have no reports from 88 or 89 yet.

Whiteboard: [not-a-fission-bug]

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.