Open Bug 1725254 Opened 4 years ago Updated 2 years ago

Launcher process: Capture early-startup errors in main process and report them

Categories

(Firefox :: Launcher Process, task, P3)

All
Windows
task

Tracking

()

ASSIGNED

People

(Reporter: cmartin, Assigned: gsvelto)

References

Details

It seems that a crash in early Main Process startup will not be reported because the Crash Reporter is not up-and-running yet, as occurred in Bug 1716743

Luckily, we already have this awesome Launcher process that is kind-of "supervising" the main process, and we already have a mechanism where a crash in a content process can be caught and reported by the main process -- Perhaps there is a way we can setup the same sort of thing between the Launcher and Main process?

It's probably not an overly high-priority task, but it seems like it would help to catch and debug early-startup crashes (perhaps caused by FF bugs or bugs from injected third-party DLLs that are known to play a bit of a cat-and-mouse game with the DLL Blocklist detour code).

Perhaps Gabriele has some thoughts on whether this is possible and how difficult of a job it would be?

Flags: needinfo?(gsvelto)
See Also: → 1682520

We will do this via WER, clearing the NI?

Flags: needinfo?(gsvelto)

Gabriele, does our WER support largely resolve this or should we reconsider this? Does having OOP crash reporting make it possible for us to handle this "easily" (more reliable and actionable than going through WER?)

Assignee: cmartin → gsvelto
Flags: needinfo?(gsvelto)

WER should catch very early startup crashes since bug 1682520 whoever there's a few limitations to it that mean it's not a complete solution: first of all it's not working on all Windows 10 versions, we noticed it only works starting with a certain build (can't remember which one off the top of my head). Additionally WER doesn't retrieve all the crash annotations from the crashed process and so startup crashes caught by WER are not marked as such (this is something that I will fix with bug 1831092). Last but not least it's only limited to Windows. So my answer is that WER partially solved this problem, but OOP crash reporting would be a more comprehensive, more reliable solution.

Flags: needinfo?(gsvelto)
You need to log in before you can comment on or make changes to this bug.