Open Bug 1868148 Opened 5 months ago Updated 2 months ago

Crash in [@ webrender::renderer::Renderer::update_deferred_resolves]

Categories

(Core :: Graphics: WebRender, defect)

Unspecified
Linux
defect

Tracking

()

People

(Reporter: gsvelto, Unassigned)

References

(Depends on 1 open bug, Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

Crash report: https://crash-stats.mozilla.org/report/index/f03a9215-56b5-4a8e-a730-6757e0231202

MOZ_CRASH Reason: Raw external data is not expected for deferred resolves!

Top 10 frames of crashing thread:

0  libxul.so  MOZ_Crash  mfbt/Assertions.h:281
0  libxul.so  RustMozCrash  mozglue/static/rust/wrappers.cpp:18
1  libxul.so  mozglue_static::panic_hook  mozglue/static/rust/lib.rs:96
2  libxul.so  core::ops::function::Fn::call  library/core/src/ops/function.rs:79
3  libxul.so  <alloc::boxed::Box<F, A> as core::ops::function::Fn<Args>>::call  library/alloc/src/boxed.rs:2021
3  libxul.so  std::panicking::rust_panic_with_hook  library/std/src/panicking.rs:735
4  libxul.so  std::panicking::begin_panic::{{closure}}  library/std/src/panicking.rs:639
5  libxul.so  std::sys_common::backtrace::__rust_end_short_backtrace  library/std/src/sys_common/backtrace.rs:170
6  libxul.so  std::panicking::begin_panic  library/std/src/panicking.rs:638
7  libxul.so  webrender::renderer::Renderer::update_deferred_resolves  gfx/wr/webrender/src/renderer/mod.rs:4231

This crash seems to have been around for a while but I only noticed it today doing nightly crash triage. Several comments point to the crash happening on https://www.flightradar24.com but there's also several URLs pointing to dashboards of some kind (all behind logins, so not publicly available).

See Also: → 1841380
Severity: -- → S3
Blocks: wr-stability
Depends on: 1870618

I had a crash with the same signature. In my case it happened when interacting my LAN-local grafana dashboard. As mentioned in 1870618, I was getting a lot of tab crashes, but at some point the whole process crashed too. I turned off hardware accel to work around it for now.

You need to log in before you can comment on or make changes to this bug.