Open Bug 1620998 (oop-crashreporter) Opened 5 years ago Updated 1 years ago

Write a crash monitor program to handle annotations and minidump writing

Categories

(Toolkit :: Crash Reporting, task)

task

Tracking

()

People

(Reporter: gsvelto, Unassigned)

References

(Blocks 9 open bugs)

Details

We should write a stand-alone program that can be launched by Firefox that will receive and gather crash annotations for the various processes and write out minidumps when requested to.

The program will have to communicate with Firefox over simple IPC. It will be able to accept a limited list of commands which will include:

  • Establishing an IPC channel with newly created processes
  • Writing out the minidump of a crashed process
  • Writing out the minidump of a running process
  • Writing out the crash annotations (.extra file) of a given process
  • Launching the crash reporter client if the main process crashes
Blocks: 1621000
Blocks: 1678591

Tentatively tracking this bug for Fission because this crash monitor may be the solution for bug 1594529 (which is blocking WebGL remoting for Fission).

Blocks: 1594529
Fission Milestone: --- → M7

(In reply to Chris Peterson [:cpeterson] from comment #1)

Tentatively tracking this bug for Fission because this crash monitor may be the solution for bug 1594529 (which is blocking WebGL remoting for Fission).

Correction: Untracking for Fission. Gabriele says this crash monitor will be a big change and he recommends that we not block Fission waiting for it.

Fission Milestone: M7 → ---
Blocks: 1683552
Depends on: 1759682
No longer depends on: 1759682
Depends on: 1776197
Severity: normal → S3
Blocks: 1816229
Alias: oop-crashreporter
Blocks: 1837903
Blocks: 1838482
You need to log in before you can comment on or make changes to this bug.