Note: There are a few cases of duplicates in user autocompletion which are being worked on.

stylo: Crash in mozalloc_abort | abort | core::result::unwrap_failed<T> | style::properties::longhands::system_font::{{impl}}::to_computed_value

NEW
Unassigned

Status

()

Core
CSS Parsing and Computation
P1
critical
11 days ago
8 days ago

People

(Reporter: cpeterson, Unassigned)

Tracking

(Blocks: 2 bugs, {crash})

54 Branch
Unspecified
Linux
crash
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox56 affected)

Details

(crash signature)

(Reporter)

Description

11 days ago
This bug was filed from the Socorro interface and is 
report bp-6bf9bef3-8cb6-448f-85ca-bf4940170709.
=============================================================

1 crash in Nightly 56
(Reporter)

Updated

11 days ago
Blocks: 1375906
unwrap_failed from system_font::to_computed_value? That's fun... I don't see any Result type inside that function directly. It is annoying that there is no crash message. My first guess would be that system.weight ends up being a number which isn't a multiple of 100, which triggers the unwrap-ish in font_weight::computed_value::T::from_gecko_weight.

We may want to remove that .expect or round it to a multiple of 100 for now.
(In reply to Xidorn Quan [:xidorn] UTC+10 from comment #1)
> unwrap_failed from system_font::to_computed_value? That's fun... I don't see
> any Result type inside that function directly. It is annoying that there is
> no crash message. My first guess would be that system.weight ends up being a
> number which isn't a multiple of 100, which triggers the unwrap-ish in
> font_weight::computed_value::T::from_gecko_weight.
> 
> We may want to remove that .expect or round it to a multiple of 100 for now.

That's an expect() though, right? That shouldn't have this crash signature...
You need to log in before you can comment on or make changes to this bug.