| components.conf |
|
871 |
| CrashManager.in.sys.mjs |
How long to wait after application startup before crash event files are
automatically aggregated.
We defer aggregation for performance reasons, as we don't want too many
services competing for I/O immediately after startup.
|
53592 |
| CrashManagerTest.sys.mjs |
This file provides common and shared functionality to facilitate
testing of the Crashes component (CrashManager.sys.mjs).
|
5036 |
| CrashService.sys.mjs |
Run the minidump-analyzer with the given options unless we're already
shutting down or the main process has been instructed to shut down in the
case a content process crashes. Minidump analysis can take a while so we
don't want to block shutdown waiting for it.
|
6931 |
| docs |
|
|
| gen_CrashManager.py |
processTypes: { |
1555 |
| metrics.yaml |
|
25627 |
| moz.build |
|
1067 |
| nsICrashService.idl |
Records the occurrence of a crash.
@param processType
One of the PROCESS_TYPE constants defined in nsIXULRuntime.
@param crashType
One of the CRASH_TYPE constants defined below.
@param id
Crash ID. Likely a UUID.
@return A promise that resolves after the crash has been stored
|
841 |
| pings.yaml |
|
1054 |
| tests |
|
|