Hit MOZ_CRASH(assertion failed: index < self.owned.len()) at /third_party/rust/wgpu-core/src/track/metadata.rs:63
Categories
(Core :: Graphics: WebGPU, defect)
Tracking
()
People
(Reporter: jkratzer, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: testcase, Whiteboard: [bugmon:bisected,confirmed])
Crash Data
Attachments
(2 files)
Reporter | ||
Comment 1•11 months ago
|
||
Reporter | ||
Comment 2•11 months ago
|
||
Comment 3•11 months ago
|
||
Got this crash : https://crash-stats.mozilla.org/report/index/c66de31a-292b-4f3f-b2af-e8b290231113#tab-bugzilla
Updated•11 months ago
|
Comment 5•11 months ago
|
||
Verified bug as reproducible on mozilla-central 20231113215623-a517db1d17ab.
Unable to bisect testcase (Testcase reproduces on start build!):
Start: 1adc82d1eb960a8a6aac68b9abceaac3fd491abb (20221115051541)
End: a517db1d17abb3981cb2c0e94ff986ecfe64211d (20231113215623)
BuildFlags: BuildFlags(asan=True, tsan=False, debug=False, fuzzing=True, coverage=False, valgrind=False, no_opt=False, fuzzilli=False, nyx=False)
Comment 6•11 months ago
|
||
Testcase crashes using the initial build (mozilla-central 20231113215623-a517db1d17ab) but not with tip (mozilla-central 20231124214933-8a861d9d1b4a.)
The bug appears to have been fixed in the following build range:
Start: 36c4a38c6d225c7315445718e62d4703c40c277a (20231120194812)
End: 7b567ceeead73f84de62ab77b4b6c87450b347fa (20231120230927)
Pushlog: https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=36c4a38c6d225c7315445718e62d4703c40c277a&tochange=7b567ceeead73f84de62ab77b4b6c87450b347fa
jkratzer, can you confirm that the above bisection range is responsible for fixing this issue?
Removing bugmon keyword as no further action possible. Please review the bug and re-add the keyword for further analysis.
Reporter | ||
Comment 7•10 months ago
|
||
:nical, I'm assuming that bug 1865585 was responsible for fixing this issue?
Comment 8•10 months ago
|
||
It probably affected it, but I'm still seeing more or less the same stack trace pop up randomly on CI so I don't think it's actually fixed.
Comment 9•9 months ago
|
||
This is now fixed.
Description
•