Closed
Bug 1889120
Opened 6 months ago
Closed 5 months ago
[siglist] Add Rust sub-slice accesses to the prefix list
Categories
(Socorro :: Signature, defect, P3)
Socorro
Signature
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ErichDonGubler, Assigned: ErichDonGubler)
Details
Attachments
(1 file)
I've noticed that some crashes are incorrectly being aggregated together because slice index accesses of slices (e.g., using a 2..4
"index" in the expr. slice[2..4]
, which I'll refer to as "sub-slice accesses" to hopefully be more clear) are not part of the prefix list. The frames that don't already appear to be part of the prefix list are:
<core::ops::range::Range<usize> as core::slice::index::SliceIndex<[T]>>::index
core::slice::index::<impl core::ops::index::Index<I> for [T]>::index
Assignee | ||
Updated•6 months ago
|
Summary: [siglist] Add Rust sub-slice accesses to the prefix list → [siglist] Add Rust sub-slice accesses to the irrelevant list
Assignee | ||
Updated•6 months ago
|
Summary: [siglist] Add Rust sub-slice accesses to the irrelevant list → [siglist] Add Rust sub-slice accesses to the prefix list
Assignee | ||
Comment 1•6 months ago
|
||
Example: bug 1885339's crash reports have frames for:
-
Report
039b22bf-6bce-423e-8996-a93560240313
should be associated with WebGPU:<core::ops::range::Range<usize> as core::slice::index::SliceIndex<[T]>>::index core::slice::index::<impl core::ops::index::Index<I> for [T]>::index wgpu_hal::metal::device::<impl wgpu_hal::Device<wgpu_hal::metal::Api> for wgpu_hal::metal::Device>::create_bind_group
-
Report
a3354fdd-a972-46d5-9407-7c3b30240329
should be associated with WebRender:<core::ops::range::Range<usize> as core::slice::index::SliceIndex<[T]>>::index core::slice::index::<impl core::ops::index::Index<I> for [T]>::index webrender::scene_building::SceneBuilder::finalize_picture
Assignee | ||
Comment 2•6 months ago
•
|
||
Filed a PR upstream at socorro
#6568. Hopefully that makes this easy. 🙂 Happy to have this assigned to me, too, if that helps.
Comment 3•6 months ago
|
||
Updated•6 months ago
|
Assignee: nobody → egubler
Status: NEW → ASSIGNED
Priority: -- → P3
Comment 4•6 months ago
|
||
Comment 5•5 months ago
|
||
This deployed to production just now in bug #1890341.
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•