Open
Bug 1893837
Opened 1 month ago
Updated 25 days ago
Crash in [@ core::ptr::drop_in_place | smallvec::impl$37::drop]
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox127 | --- | affected |
People
(Reporter: release-mgmt-account-bot, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/6e437900-0d43-4c7c-bdcf-fb57d0240424
MOZ_CRASH Reason: Locked::read_with called with a guard from an unrelated SharedRwLock: 0x11 vs. 0x1d8e580
Top 10 frames of crashing thread:
0 xul.dll MOZ_Crash mfbt/Assertions.h:317
0 xul.dll RustMozCrash mozglue/static/rust/wrappers.cpp:17
1 xul.dll mozglue_static::panic_hook mozglue/static/rust/lib.rs:98
2 xul.dll core::ops::function::Fn::call<void /rustc/25ef9e3d85d934b27d9dada2f9dd52b1dc63bb04/library/core/src/ops/function.rs:250
3 xul.dll alloc::boxed::impl$49::call library/alloc/src/boxed.rs:2029
3 xul.dll std::panicking::rust_panic_with_hook library/std/src/panicking.rs:785
4 xul.dll std::panicking::begin_panic_handler::closure$0 library/std/src/panicking.rs:659
5 xul.dll std::sys_common::backtrace::__rust_end_short_backtrace<std::panicking::begin_panic_handler::closure_env$0, never$> library/std/src/sys_common/backtrace.rs:171
6 xul.dll std::panicking::begin_panic_handler library/std/src/panicking.rs:647
7 xul.dll core::panicking::panic_fmt library/core/src/panicking.rs:72
By querying Nightly crashes reported within the last 2 months, here are some insights about the signature:
- First crash report: 2024-02-21
- Process type: Content
- Is startup crash: No
- Has user comments: No
- Is null crash: No
Updated•1 month ago
|
Component: General → CSS Parsing and Computation
Comment 1•25 days ago
|
||
Seems to be a low but fairly steady crash rate since late-ish January (perhaps corresponding to the release of Firefox 124), though there are some reports from earlier versions as well, so not entirely a new issue.
Severity: -- → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•