Closed Bug 1573053 Opened 5 years ago Closed 5 years ago

Crash in [@ webrender::render_backend::DataStores::as_common_data]

Categories

(Core :: Graphics: WebRender, defect, P3)

Unspecified
Windows 10
defect

Tracking

()

RESOLVED INVALID
Tracking Status
firefox70 --- affected

People

(Reporter: gsvelto, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: crash)

Crash Data

This bug is for crash report bp-857cc123-cca2-423c-8caf-e11c70190811.

Top 10 frames of crashing thread:

0 xul.dll GeckoCrash toolkit/xre/nsAppRunner.cpp:5148
1 xul.dll static void gkrust_shared::panic_hook toolkit/library/rust/shared/lib.rs:248
2 xul.dll static void core::ops::function::Fn::call<fn src/libcore/ops/function.rs:69
3 xul.dll static void std::panicking::rust_panic_with_hook src/libstd/panicking.rs:478
4 xul.dll static void std::panicking::continue_panic_fmt src/libstd/panicking.rs:381
5 xul.dll static void std::panicking::rust_begin_panic src/libstd/panicking.rs:308
6 xul.dll static void core::panicking::panic_fmt src/libcore/panicking.rs:85
7 xul.dll void core::panicking::panic_bounds_check src/libcore/panicking.rs:61
8 xul.dll static struct webrender::prim_store::PrimTemplateCommonData* webrender::render_backend::DataStores::as_common_data gfx/wr/webrender/src/render_backend.rs
9 xul.dll static union core::option::Option<euclid::rect::Rect<f32, webrender_api::units::PicturePixel>> webrender::prim_store::PrimitiveStore::update_visibility gfx/wr/webrender/src/prim_store/mod.rs:1958

The raw MOZ_CRASH_REASON for this crashes is an out-of-bounds access. This one for example is:

index out of bounds: the len is 78 but the index is 8388611

However there's quite a bit of variance in both the index value and array length among the crashes.

Other index out of bounds crashes.

Blocks: wr-70
Priority: -- → P3

Similarly to bug 1563609, it looks like this is AMD-specifc, which is a bit worrying.

Looking at the crashes again they all have the same CPU info field (family 23 model 1 stepping 1), same memory size and same graphics adapter. This might be an invalid one, a single-installation crash caused by faulty hardware.

(In reply to Nicolas Silva [:nical] from comment #2)

Similarly to bug 1563609, it looks like this is AMD-specifc, which is a bit worrying.

Nevermind, it looks like most of the crashes come from the same user who happens to use an AMD CPU.
Edit: My comment raced with Gabriele's. Yeah I agree.

I was about to close this as a single-installation crash but I noticed a different type of crash under this signature:

https://crash-stats.mozilla.org/report/index/928f28a8-5282-4d74-957e-298340190914

The raw crash reason is: internal error: entered unreachable code and we've hit it here:

https://hg.mozilla.org/releases/mozilla-release/annotate/cce4622026ab8e0130a0afc03f829f9b19ca38c2/gfx/wr/webrender/src/render_backend.rs#l308

I'll leave this open for a while in case the crashes are actually meaningful.

No longer blocks: wr-70

The crashes keep coming from a single machine, let's close this and reopen another bug if we get different crashes under this signature.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.