Crash in [@ core::option::expect_failed | chrono::offset::local::Local::now]
Categories
(Toolkit :: Telemetry, defect, P3)
Tracking
()
People
(Reporter: gsvelto, Unassigned)
References
Details
(Keywords: crash, Whiteboard: [telemetry:glean-rs:m?])
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/fadd5970-ae51-4bf2-9fc2-fcda70200912
Top 10 frames of crashing thread:
0 xul.dll RustMozCrash mozglue/static/rust/wrappers.cpp:16
1 xul.dll mozglue_static::panic_hook mozglue/static/rust/lib.rs:89
2 xul.dll core::ops::function::Fn::call<fn ../4fb7144ed159f94491249e86d5bbd033b5d60550/src/libcore/ops/function.rs:232
3 xul.dll std::panicking::rust_panic_with_hook ../4fb7144ed159f94491249e86d5bbd033b5d60550//src/libstd/panicking.rs:474
4 xul.dll std::panicking::begin_panic_handler ../4fb7144ed159f94491249e86d5bbd033b5d60550//src/libstd/panicking.rs:378
5 xul.dll core::panicking::panic_fmt ../4fb7144ed159f94491249e86d5bbd033b5d60550//src/libstd/panicking.rs:332
6 xul.dll core::option::expect_failed ../4fb7144ed159f94491249e86d5bbd033b5d60550//src/libcore/option.rs:1203
7 xul.dll static chrono::offset::local::Local::now third_party/rust/chrono/src/offset/local.rs:93
8 xul.dll glean_core::Glean::new_for_subprocess third_party/rust/glean-core/src/lib.rs:218
9 xul.dll once_cell::imp::{{impl}}::initialize::{{closure}}<fog_control::api::AppState, closure-0, glean_core::error::Error> third_party/rust/once_cell/src/imp_std.rs:97
Crashes are coming from only one user but the issue looks valid. The raw crash reason is FixedOffset::east out of bounds which is happening in this conversion.
I remember filing a similar crash some time ago but I can't find it right now.
|
||
Comment 1•4 years ago
|
||
Looks similar to bug 1611770
|
||
Updated•4 years ago
|
|
||
Comment 2•4 years ago
|
||
As you mentioned in bug 1611770 c#2, we could try catch_unwind... but only if panic is unwind not abort. I know some test configs (ccov and geckodriver) run with panic abort, but do any of our (or our distributors') builds do as well?
|
|
||
Comment 3•4 years ago
|
||
Seems as though this single client went away. When bug 1651111 hits beta we might finally get enough information to explain what's going on.
Description
•