If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Improve the logging in IPC when we crash

RESOLVED WONTFIX

Status

()

Core
IPC
RESOLVED WONTFIX
4 years ago
6 months ago

People

(Reporter: gkw, Unassigned)

Tracking

Trunk
ARM
Gonk (Firefox OS)
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
Improve the logging in IPC when we crash. For example, when we crashed at mozilla::dom::ContentChild::ProcessingError in bug 878366, we "need to know the message id (combination of protocol type and message type)" to get anything useful, and currently the only way to do it is to break into the debugger.

However, the crash was on a Unagi testdriver device, which is unlikely to be attached to a debugger during the crash.

I don't have much specifics here, so maybe bent can elaborate what he meant in bug 878366 comment 6.

Updated

4 years ago
Blocks: 878366
(Reporter)

Comment 1

4 years ago
Nominating as per bug 878366 comment 19 / 20.
blocking-b2g: - → koi?

Comment 2

4 years ago
Things I want to see:
* destination actor IDs for every message sent
* report the failed ID when a routing error occurs
* a message ID that can associate a message receipt failure with a message send
I think bug 878366 can get by without a proper fix here (which is still needed) so I'm going to remove the koi nom.
blocking-b2g: koi? → 1.3?
Andrew,

What is the user impact here?
Flags: needinfo?(overholt)
There's no direct user impact.  This would greatly help with diagnosing issues, though.

I doubt it's the kind of thing we'd hold the release for (so I'm removing 1.3?) but I'd still really like to see it happen so I'll work with Ben to keep it on his -- and others' -- radar.
blocking-b2g: 1.3? → ---
Flags: needinfo?(overholt)
I think Ted is going to take a look here!
(Reporter)

Updated

6 months ago
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.