Open
Bug 1844377
Opened 2 years ago
Updated 1 year ago
Crash in [@ core::ops::function::impls::impl$3::call_mut]
Categories
(Data Platform and Tools :: Glean: SDK, defect, P4)
Tracking
(Not tracked)
NEW
People
(Reporter: ryanvm, Unassigned)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/aaabcad3-43b1-4c5c-b883-f70670230709
Reason: EXCEPTION_STACK_BUFFER_OVERRUN / FAST_FAIL_GUARD_ICALL_CHECK_FAILURE
Top 10 frames of crashing thread:
0 ntdll.dll RtlFailFast2
1 ntdll.dll RtlpHandleInvalidUserCallTarget
2 ntdll.dll LdrpHandleInvalidUserCallTarget
3 xul.dll core::ops::function::impls::impl$3::call_mut /rustc/84c898d65adf2f39a5a98507f1fe0ce10a2b8dbc/library/core/src/ops/function.rs:298
3 xul.dll once_cell::imp::initialize_or_wait third_party/rust/once_cell/src/imp_std.rs:206
4 xul.dll once_cell::imp::OnceCell<std::sync::mutex::Mutex<alloc::vec::Vec<glean_core::metrics::ping::PingType, alloc::alloc::Global> > >::initialize third_party/rust/once_cell/src/imp_std.rs:78
4 xul.dll once_cell::sync::OnceCell<std::sync::mutex::Mutex<alloc::vec::Vec<glean_core::metrics::ping::PingType, alloc::alloc::Global> > >::get_or_try_init third_party/rust/once_cell/src/lib.rs:1129
4 xul.dll once_cell::sync::OnceCell<std::sync::mutex::Mutex<alloc::vec::Vec<glean_core::metrics::ping::PingType, alloc::alloc::Global> > >::get_or_init third_party/rust/once_cell/src/lib.rs:1088
4 xul.dll glean_core::register_ping_type third_party/rust/glean-core/src/lib.rs:777
5 xul.dll glean_core::metrics::ping::PingType::new third_party/rust/glean-core/src/metrics/ping.rs:71
Comment 1•2 years ago
|
||
Gonna spend a couple cycles looking at what's with this. Should be impossible in Rust (unless the rust impl is buggy).
Assignee: nobody → chutten
Severity: -- → S4
Status: NEW → ASSIGNED
Priority: -- → P1
Comment 2•1 year ago
|
||
Still no idea what's going on. Still Windows-only (10 and 11). Still happening in current code. Still infrequent.
Assignee: chutten → nobody
Status: ASSIGNED → NEW
Priority: P1 → P4
You need to log in
before you can comment on or make changes to this bug.
Description
•