Open Bug 1306983 Opened 8 years ago Updated 2 years ago

Add IPDL protocol errors to crash report metadata

Categories

(Toolkit :: Crash Reporting, defect)

defect

Tracking

()

People

(Reporter: jdm, Unassigned)

Details

Currently, if a call to ReadActor from deserialization routines fails, it internally calls ProtocolErrorBreakpoint with a message, and that message gets printed to stderr. ReadActor then returns false, and the deserialization routine returns false, so we hit the FatalError code path that tells us something like "IPD FatalError in the parent process", which is much less useful than the message that was printed to stderr. This would make the crashes like https://crash-stats.mozilla.com/report/index/36d4ac2f-5745-4cc0-8a96-4644b2161001#tab-details easier to diagnose.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.