Closed Bug 1757605 Opened 3 years ago Closed 3 years ago

Add mozilla::ipc::SentinelReadError to the prefix list

Categories

(Socorro :: Signature, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: mccr8, Assigned: willkg)

References

Details

Attachments

(1 file)

In bug 1757534, we had a crash regression land in Nightly, but nobody noticed it for a little over a month. There was a steady trickle of crashes, but presumably because it only affected ARM64 Windows 10, there was not enough volume to catch anybody's attention. Probably part of the issue is that this is a rather generic signature, combining a number of IPC serialization issues. Maybe regressions in these sorts of crashes would be more noticeable if we add mozilla::ipc::SentinelReadError to the prefix list.

Here's an example of these crashes: bp-32f63301-804f-4e9d-ba52-bfb670220301

With this addition to the prefix list, I think the signature would go from [@ mozilla::ipc::SentinelReadError] to [@mozilla::ipc::SentinelReadError | mozilla::ipc::SentinelReadError | mozilla::gmp::PGMPParent::OnMessageReceived]. The double SentinelReadError isn't great, but I think it is nice to have an indication that this is specifically a deserialization error, and not some other kind of unknown crash.

Grabbing this to do now.

Assignee: nobody → willkg
Status: NEW → ASSIGNED
Priority: -- → P2

Thanks!

I deployed this to prod just now in bug #1759160. Marking as FIXED.

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

Attachment

General

Created:
Updated:
Size: