Closed Bug 1383054 Opened 8 years ago Closed 8 years ago

Stylo: Crash in alloc::oom::default_oom_handler | style::context::ElementCascadeInputs::new_from_element_data

Categories

(Core :: CSS Parsing and Computation, defect)

Product:
Core
Component:
CSS Parsing and Computation
Platform:
Unspecified
Windows 10
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1383001

People

(Reporter: jseward, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is report bp-450a7dea-7289-46df-ba98-a67600170721. ============================================================= This is topcrash #17 in the Windows nightly of 20170720030203. Looks like Stylo is OOMing.
Flags: needinfo?(bobbyholley)
Summary: Crash in alloc::oom::default_oom_handler | style::context::ElementCascadeInputs::new_from_element_data → Stylo: Crash in alloc::oom::default_oom_handler | style::context::ElementCascadeInputs::new_from_element_data
This looks like it could be a duplicate of bug 1383001. Can anyone confirm if this the case?
(In reply to Julian Seward [:jseward] from comment #0) > Looks like Stylo is OOMing. The Rust equivalent of MOZ_CRASH just shows up as default_oom_handler for whatever reason. Note that the crash report you linked has MOZ_CRASH Reason of "called `Option::unwrap()` on a `None` value".
(In reply to Ryan Jones [:sciguyryan] from comment #1) > This looks like it could be a duplicate of bug 1383001. Can anyone confirm > if this the case? Yeah, that sounds right. I recall reading that the crash signature show up differently sometimes.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(bobbyholley)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.