fune/toolkit/components/crashes
Gabriele Svelto d91b14fc7a Bug 1393716 - Don't run minidump analysis on content crashes if the browser is quitting r=ted.mielczarek
When a content crash is detected we run the minidump analyzer on it to extract
a stack trace that will be sent with the crash ping. Since this operation can
potentially take a long time this patch prevents it from happening if the
browser is already quitting. Already running instances of the minidump
analyzer are also killed. The patch includes test coverage for both the new
codepaths.

MozReview-Commit-ID: 4CQBp0v5KxE

--HG--
extra : rebase_source : 430d4ddad0780fe8fa0adfc8dd6728ab2eadbeaf
extra : amend_source : 3468542ab80d29cf98dfe9e10185215fedbe03b8
2017-09-03 10:48:18 +02:00
..
docs
tests/xpcshell Bug 1393716 - Don't run minidump analysis on content crashes if the browser is quitting r=ted.mielczarek 2017-09-03 10:48:18 +02:00
CrashManager.jsm Bug 1353168 - Add a crash annotation to distinguish between web, file and extension content processes; r=bsmedberg 2017-06-01 11:16:11 +02:00
CrashManagerTest.jsm Bug 1368456 - Remove imports of Promise.jsm from Firefox, r=mconley. 2017-06-23 11:25:18 +02:00
CrashService.js Bug 1393716 - Don't run minidump analysis on content crashes if the browser is quitting r=ted.mielczarek 2017-09-03 10:48:18 +02:00
CrashService.manifest
moz.build
nsICrashService.idl