Open
Bug 1868252
Opened 2 years ago
Updated 2 years ago
Crash in [@ core::option::expect_failed | webrender::hit_test::HitTester::hit_test]
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
NEW
| Tracking | Status | |
|---|---|---|
| firefox122 | --- | affected |
People
(Reporter: release-mgmt-account-bot, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: crash)
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/1d8978bd-c85b-4a0b-a0cf-a4bcf0231204
MOZ_CRASH Reason: no entry found for key
Top 10 frames of crashing thread:
0 xul.dll MOZ_Crash mfbt/Assertions.h:281
0 xul.dll RustMozCrash mozglue/static/rust/wrappers.cpp:17
1 xul.dll mozglue_static::panic_hook mozglue/static/rust/lib.rs:96
2 xul.dll core::ops::function::Fn::call<void /rustc/79e9716c980570bfd1f666e3b16ac583f0168962/library/core/src/ops/function.rs:250
3 xul.dll alloc::boxed::impl$49::call library/alloc/src/boxed.rs:2021
3 xul.dll std::panicking::rust_panic_with_hook library/std/src/panicking.rs:735
4 xul.dll std::panicking::begin_panic_handler::closure$0 library/std/src/panicking.rs:609
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:170
6 xul.dll std::panicking::begin_panic_handler library/std/src/panicking.rs:597
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: 2023-11-28
- Process type: Multiple distinct types
- Is startup crash: No
- Has user comments: No
- Is null crash: Yes - 1 out of 2 crashes happened on null or near null memory address
| Reporter | ||
Comment 1•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Graphics: WebRender' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Component: General → Graphics: WebRender
Comment 2•2 years ago
|
||
Lots of very old machines affected, this is most likely caused by bad hardware.
Updated•2 years ago
|
Severity: -- → S3
Updated•2 years ago
|
Blocks: wr-stability
You need to log in
before you can comment on or make changes to this bug.
Description
•