Open
Bug 1342578
Opened 7 years ago
Updated 2 years ago
Crash in nsDisplayListBuilder::MarkFramesForDisplayList
Categories
(Core :: Layout, defect)
Tracking
()
People
(Reporter: philipp, Unassigned)
Details
(Keywords: crash)
Crash Data
This bug was filed from the Socorro interface and is report bp-772a1886-bffe-45a5-aca7-0fbce2170224. ============================================================= Crashing Thread (0) Frame Module Signature Source 0 xul.dll nsDisplayListBuilder::MarkFramesForDisplayList(nsIFrame*, nsFrameList const&, nsRect const&) layout/base/nsDisplayList.cpp:1058 1 xul.dll nsIFrame::MarkAbsoluteFramesForDisplayList(nsDisplayListBuilder*, nsRect const&) layout/generic/nsFrame.cpp:2946 2 xul.dll nsIFrame::BuildDisplayListForChild(nsDisplayListBuilder*, nsIFrame*, nsRect const&, nsDisplayListSet const&, unsigned int) layout/generic/nsFrame.cpp:2845 3 @0x36 4 @0x80000063 these crashes have been happening for a while already, mainly on windows and in the content process. they are rather low volume though, in 51.0.1 they were accounting for 0.2% of content crashes last week. Correlations for Firefox Release: (86.50% in signature vs 30.74% overall) process_type = content [50.74% vs 124.60% if startup_crash = null] (80.59% in signature vs 10.46% overall) address = 0x0 (99.58% in signature vs 35.96% overall) reason = EXCEPTION_ACCESS_VIOLATION_READ
Comment 1•7 years ago
|
||
Too late for firefox 52, mass-wontfix.
Comment 2•3 years ago
|
||
Closing this as resolved:worksforme since there were no crashes in the last 6 months for this signature.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → WORKSFORME
Comment 3•3 years ago
|
||
I'll Reopen this bug again. There have been crashes with this signature.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Comment 4•3 years ago
|
||
example - version 91.0.2 bp-8ec4effa-c37b-42a2-ae07-cf46e0210901
Comment 5•2 years ago
|
||
Since the crash volume is low (less than 5 per week), the severity is downgraded to S3
. Feel free to change it back if you think the bug is still critical.
For more information, please visit auto_nag documentation.
Severity: critical → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•