Closed
Bug 1508714
Opened 6 years ago
Closed 6 years ago
Crash in core::option::expect_failed | <core::iter::Map<I, F> as core::iter::iterator::Iterator>::next
Categories
(Core :: Graphics: WebRender, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1492241
People
(Reporter: jan, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: crash, nightly-community)
Crash Data
GTX1060, KDE, Debian Testing
I opened https://treeherder.mozilla.org/, scrolled to the bottom, clicked on "Get Next 50", scrolled further down. My computer got slow as Nightly took a lot of CPU and memory, so I closed that tab and freed memory on about:memory.
Half a minute later I swiched to a tab of https://treeherder.mozilla.org/#/jobs?repo=try&author=kgupta%40mozilla.com&selectedJob=212892339 and got a GPU process crash.
This bug was filed from the Socorro interface and is
report bp-32351114-a0c4-4d40-a587-f7ef10181120.
> no entry found for key
> GraphicsCriticalError |[G0][GFX1-]: Updating unknown shared surface: 408021894875 (t=5888.44)
=============================================================
Top 10 frames of crashing thread:
0 libxul.so MOZ_CrashOOL mfbt/Assertions.h:311
1 libxul.so GeckoCrashOOL toolkit/xre/nsAppRunner.cpp:5350
2 libxul.so gkrust_shared::panic_hook toolkit/library/rust/shared/lib.rs:234
3 libxul.so core::ops::function::Fn::call libcore/ops/function.rs:78
4 libxul.so std::panicking::rust_panic_with_hook /rustc/da5f414c2c0bfe5198934493f04c676e2b23ff2e/src/libstd/panicking.rs:481
5 libxul.so std::panicking::continue_panic_fmt /rustc/da5f414c2c0bfe5198934493f04c676e2b23ff2e/src/libstd/panicking.rs:391
6 libxul.so rust_begin_unwind /rustc/da5f414c2c0bfe5198934493f04c676e2b23ff2e/src/libstd/panicking.rs:326
7 libxul.so core::panicking::panic_fmt /rustc/da5f414c2c0bfe5198934493f04c676e2b23ff2e/src/libcore/panicking.rs:77
8 libxul.so core::option::expect_failed /rustc/da5f414c2c0bfe5198934493f04c676e2b23ff2e/src/libcore/option.rs:1000
9 libxul.so <core::iter::Map<I, F> as core::iter::iterator::Iterator>::next libcore/option.rs:312
=============================================================
Reporter | ||
Comment 1•6 years ago
|
||
According to Socorro (Bugzilla Crash Stop) and Mozregression:
last build without this crash signature: 20181119100448
first build with this crash signature: 20181119220031
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=e44bb5b4bc79be613d29b3f95d7b508e68e3d128&tochange=bd4cebdbed4bcd34d449f67d51f139f9bdf75edc
Comment 2•6 years ago
|
||
I think this is the same problem as bug 1492241, different signature for different platform. Combined this is probably the #1 WR topcrash.
Comment 3•6 years ago
|
||
just experienced this crash: https://crash-stats.mozilla.com/report/index/436d002f-89f1-4895-880d-934a50181125#tab-details
Updated•6 years ago
|
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•