1588120 - Crash in [@ core::iter::traits::iterator::Iterator::try_fold<T>]

Status: RESOLVED WORKSFORME

(Core :: CSS Parsing and Computation, defect)

Description

[Marcia Knous [:marcia]]

This bug is for crash report bp-e65eeb82-1d76-458b-9cd7-75cb00191010.

Seen while looking at 71 crash stats - crashes go back to at least 20190903094847 on 71 and were present in 70.0a1 as well. Small volume of crashes in 70 beta. One comment "restarting after update"

Moz crash reason:

MOZ_DIAGNOSTIC_ASSERT(aDescriptor.Id() == mDescriptor.Id())

Top 10 frames of crashing thread:

0 xul.dll GeckoCrash toolkit/xre/nsAppRunner.cpp:5116
1 xul.dll static void gkrust_shared::panic_hook toolkit/library/rust/shared/lib.rs:249
2 xul.dll static void core::ops::function::Fn::call<fn src/libcore/ops/function.rs:69
3 xul.dll static void std::panicking::rust_panic_with_hook src/libstd/panicking.rs:481
4 xul.dll static void std::panicking::continue_panic_fmt src/libstd/panicking.rs:384
5 xul.dll static void std::panicking::rust_begin_panic src/libstd/panicking.rs:311
6 xul.dll static void core::panicking::panic_fmt src/libcore/panicking.rs:85
7 xul.dll void core::panicking::panic_bounds_check src/libcore/panicking.rs:61
8 xul.dll static union core::result::Result< src/libcore/iter/traits/iterator.rs:1576
9 xul.dll static union core::option::Option<rayon_core::job::JobRef> rayon_core::registry::WorkerThread::steal third_party/rust/rayon-core/src/registry.rs:759

Comment 1

[Andrew Sutherland [:asuth] (he/him)]

The line "MOZ_DIAGNOSTIC_ASSERT(aDescriptor.Id() == mDescriptor.Id())" is a ServiceWorker thing (bug 1588357 whose subject I'll update now to make it easier to find), but the crash signature and linked crashes are all Stylo crashes or some other CSS thing. They happen on style threads like "StyleThread#0" and involve rust code (of which ServiceWorkers regrettably has none). Moving and needinfo-ing for re-triage or duping as appropriate.

Comment 2

[Marcia Knous [:marcia]]

This is small enough volume that I think we can close this one out. We discussed this bug during Platform triage today and it was won't fixed for 71.