Closed Bug 1628124 Opened 5 years ago Closed 5 years ago

Do not run the minidump-analyzer when MOZ_CRASHREPORTER_SHUTDOWN is set

Categories

(Toolkit :: Crash Reporting, enhancement, P1)

enhancement

Tracking

()

RESOLVED FIXED
mozilla77
Tracking Status
firefox77 --- fixed

People

(Reporter: gsvelto, Assigned: gsvelto)

References

Details

Attachments

(1 file)

As we discussed in person with :tsmith and in bug 1596210 comment 7 and 8 there's no point in running the minidump-analyzer if we already know that the main process is shutting down and it's only causing problems so let's not run it at all.

Assignee: nobody → gsvelto
Status: NEW → ASSIGNED

When MOZ_CRASHREPORTER_SHUTDOWN is set the main process will shut down as soon
as it detects a content process crash. We usually run the minidump-analyzer
tool for every content process crash but we stop it if we detect we're
shutting down. This is done to prevent hangs because minidump analysis may
take a while.

This patch checks for MOZ_CRASHREPORTER_SHUTDOWN and does not start the
minidump-analyzer at all if it's set. Since we know we'll be shutting down
anyway there's no point in try to run it.

I took the liberty of refactoring some of the surrounding code for better
readability.

Pushed by gsvelto@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/2ac3889b41cf Do not run minidump analysis when we've instructed the browser to shut down after a content process crash r=mconley
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla77
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: