1811968 - Crash in [@ cssparser::parser::parse_nested_block]

Status: NEW

(Core :: CSS Parsing and Computation, defect)

Description

[Daniel Holbert [:dholbert]]

Crash report: https://crash-stats.mozilla.org/report/index/c41c1eec-2d8e-481d-b3b5-8a8fc0230123

Reason: EXCEPTION_ACCESS_VIOLATION_READ

Top 10 frames of crashing thread:

0  xul.dll  cssparser::parser::parse_nested_block  third_party/rust/cssparser/src/parser.rs:1043
0  xul.dll  cssparser::parser::Parser::parse_nested_block  third_party/rust/cssparser/src/parser.rs:689
0  xul.dll  style::custom_properties::substitute_block  servo/components/style/custom_properties.rs:1070
1  xul.dll  style::custom_properties::substitute_references_in_value  servo/components/style/custom_properties.rs:1009
2  xul.dll  style::custom_properties::substitute_all::traverse  servo/components/style/custom_properties.rs:965
3  xul.dll  style::custom_properties::substitute_all  servo/components/style/custom_properties.rs:992
3  xul.dll  style::custom_properties::CustomPropertiesBuilder::build  servo/components/style/custom_properties.rs:769
4  xul.dll  style::properties::cascade::apply_declarations  servo/components/style/properties/cascade.rs:281
4  xul.dll  style::properties::cascade::cascade_rules  servo/components/style/properties/cascade.rs:194
4  xul.dll  style::properties::cascade::cascade  servo/components/style/properties/cascade.rs:72

Note that we had bug 1801006 tracking a mysterious huge spike with this crash signature that was specific to Samsung Android devices with android board: exynos990, but that crash volume went away in versions 108 and newer (though there's still a slow trickle of crashes on that hardware for people still running v107).

Anyway: I'm filing this bug here to track the remaining small crash volume, setting those device-and-version-specific instance of this crash aside as being their own special thing. (If that Samsung/exynos990 issue happens to come back, we can reopen bug 1801006 to further discuss what might be going on there & possible mitigations, etc.)

Here's my search query for the last month of crash data with this signature that don't have the android board field
set (to avoid picking up straggling bug 1801006 crashes).
I see just 5 crashes, all on Windows:
bp-c41c1eec-2d8e-481d-b3b5-8a8fc0230123
bp-af534449-5c98-44f2-8037-de9a60230108
bp-8157df99-28da-4023-a822-bb2530230108
bp-845905d1-8efc-4f3a-8b63-a7d2e0230104
bp-a97a9bc9-6246-48a5-8a03-76ae90221230

None of them have user comments, and only one has a URL set (for an Google Image search results page, which doesn't trigger any trouble for me when I load it directly). So, no clues there about STR or what might be going on.