Closed
Bug 1466725
Opened 7 years ago
Closed 7 years ago
Crash in @0x0 | _$LT$style..style_resolver..StyleResolverForElement$LT$$u27$a$C$$u20$$u27$ctx$C$$u20$$u27$le$C$$u20$E$GT$$GT$::cascade_style_and_visited::h1e8a438892b22fb2
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox61 | --- | fix-optional |
People
(Reporter: marcia, Unassigned)
References
Details
(Keywords: crash, regression)
Crash Data
This bug was filed from the Socorro interface and is
report bp-d8cabcb6-e67a-4d74-9272-86a2e0180531.
=============================================================
New Fennec crash signature which appears only in B9: https://bit.ly/2swuq29. 77 crashes/44 installations. Similar signature to Bug 1451741 which appeared back in 60 and then went away.
Comments: Reading a github repo
Top 3 frames of crashing thread:
0 @0x0
1 libxul.so _$LT$style..style_resolver..StyleResolverForElement$LT$$u27$a$C$$u20$$u27$ctx$C$$u20$$u27$le$C$$u20$E$GT$$GT$::cascade_style_and_visited::h1e8a438892b22fb2 servo/components/style/style_resolver.rs:304
2 dalvik-main space 1 (deleted) dalvik-main space 1 @0xe7ffffe
=============================================================
Comment 1•7 years ago
|
||
May be related to bug 1466406. In particular, if we get away without crashing from there, we may crash around here without too much trouble I'd think.
Comment 2•7 years ago
|
||
Oh, this is beta, let's forget that. So this is only on a single build and also on a single CPU model, interesting...
Updated•7 years ago
|
Reporter | ||
Comment 3•7 years ago
|
||
This is starting to show up in 61 b11, so for now it is not limited to a single beta build.
Comment 4•7 years ago
|
||
I looked at 10 or so of the crash stacks and they were all completely bogus.
This crash could be just about anything; not necessarily style system at all.
Comment 6•7 years ago
|
||
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•