Open Bug 1508265 Opened 6 years ago Updated 2 years ago

Re-enable getting minidumps of hung content processes on shutdown

Categories

(Toolkit :: Crash Reporting, enhancement)

enhancement

Tracking

()

Tracking Status
firefox65 --- affected

People

(Reporter: gsvelto, Unassigned)

References

Details

+++ This bug was initially created as a clone of Bug #1498942 +++

We've disabled the generation of minidumps for hung content processes during shutdown to prevent bug 1498942 from happening again. Since those minidumps might be valuable - in case of content processes that are really getting stuck during shutdown - we should re-enable it when possible. One way to avoid the "avalanche-of-minidumps" issue we saw in bug 1498942 is to allow for only one minidump to be generated for the first content process that is detected as stuck. After that other processes that appear as stuck will just be killed. In the unlikely case that all the content processes are actually stuck there's a good chance that it's for the same reason so we don't need more minidumps anyway.

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: critical → --
Severity: -- → S3
You need to log in before you can comment on or make changes to this bug.