Crash in [@ peek_poke::peek_from_slice<T>]
Categories
(Core :: Graphics: WebRender, defect, P3)
Tracking
()
People
(Reporter: toadking, Unassigned)
References
(Blocks 1 open bug)
Details
Crash Data
Crash report: https://crash-stats.mozilla.org/report/index/c5fe4ecb-865d-4708-8cfa-4f1ba0210323
MOZ_CRASH Reason: WRDL: memory corruption detected while parsing DisplayItem - enum tag should be <= 33, but was 76
Top 10 frames of crashing thread:
0 xul.dll RustMozCrash mozglue/static/rust/wrappers.cpp:16
1 xul.dll mozglue_static::panic_hook mozglue/static/rust/lib.rs:89
2 xul.dll core::ops::function::Fn::call<fn ../cb75ad5db02783e8b0222fee363c5f63f7e2cf5b/library/core/src/ops/function.rs:227
3 xul.dll std::panicking::rust_panic_with_hook ../cb75ad5db02783e8b0222fee363c5f63f7e2cf5b//library/std/src/panicking.rs:595
4 xul.dll std::panicking::begin_panic_handler::{{closure}} ../cb75ad5db02783e8b0222fee363c5f63f7e2cf5b//library/std/src/panicking.rs:497
5 xul.dll std::sys_common::backtrace::__rust_end_short_backtrace<closure-0, !> ../cb75ad5db02783e8b0222fee363c5f63f7e2cf5b//library/std/src/sys_common/backtrace.rs:141
6 xul.dll std::panicking::begin_panic_handler ../cb75ad5db02783e8b0222fee363c5f63f7e2cf5b//library/std/src/panicking.rs:493
7 xul.dll std::panicking::begin_panic_fmt ../cb75ad5db02783e8b0222fee363c5f63f7e2cf5b//library/std/src/panicking.rs:435
8 xul.dll peek_poke::peek_from_slice<webrender_api::display_item::DisplayItem> gfx/wr/peek-poke/src/lib.rs:57
9 xul.dll webrender_api::display_list::BuiltDisplayListIter::next_raw gfx/wr/webrender_api/src/display_list.rs:652
Been getting crashes regularly (multiple times an hour) after upgrading to 88.0b1.
|
Reporter | |
Comment 2•4 years ago
|
||
Yes, I was able to reproduce it in Nightly.
https://crash-stats.mozilla.org/report/index/ab45f6c3-8bcb-4124-8ad4-a38790210323
|
||
Comment 3•4 years ago
|
||
Can you find a regression window using https://mozilla.github.io/mozregression/?
|
|
||
Comment 4•4 years ago
|
||
It might be a bit tricky given that it doesn't reproduce deterministically.
|
|
Reporter | |
Comment 5•4 years ago
|
||
I can try but it seems to come and go in bursts for some reason.
I also started getting a whole bunch of seemingly unrelated crashes as well. Maybe something got messed up with my profile or install.
https://crash-stats.mozilla.org/report/index/f51f0869-5f98-4a58-8d98-7530d0210323
https://crash-stats.mozilla.org/report/index/f3e19123-c42f-41a5-a2c2-0c8680210323
https://crash-stats.mozilla.org/report/index/a63991f8-2cf4-40a4-a028-096590210323
https://crash-stats.mozilla.org/report/index/c00be7c7-4c07-4eb2-b143-9670e0210323
|
|
||
Comment 6•4 years ago
|
||
Maybe you're having RAM corruption of some kind? You could try running some older versions like 87 and 86 and see if you see the issue there. Also interesting would be to try a fresh profile.
|
||
Updated•4 years ago
|
|
|
Reporter | |
Comment 7•4 years ago
|
||
I'm not sure this is actually a WebRender bug anymore. I'm starting to get all these wild crashes in Firefox that suddenly started happening yesterday, on both release versions and nightlies.
https://crash-stats.mozilla.org/report/index/c109eec6-a39c-45b6-874f-11cd80210324
https://crash-stats.mozilla.org/report/index/2a96f403-c19e-4b27-9f40-82a2e0210324
https://crash-stats.mozilla.org/report/index/03529708-0468-43b6-9016-4b0920210324
https://crash-stats.mozilla.org/report/index/b310a32d-3e90-48d0-837e-1cafb0210324
I ran a memtest that passed and no other apps are having problems so I don't think it's my hardware. I have no idea what it could be at this point.
|
||
Updated•4 years ago
|
|
|
||
Updated•4 years ago
|
|
|
Reporter | |
Comment 9•4 years ago
|
||
I'm unsure what's changed on my machine but I haven't had any crashes since my last update. (Except for one related to #1700614) If nobody else is having these issues then maybe this is good to close?
|
||
Comment 10•3 years ago
|
||
The bug has a crash signature, thus the bug will be considered confirmed.
Description
•