Description of Change

This refactors crashReporter, making the following changes:

1. Calling crashReporter.start from the renderer process is now deprecated, and only has the effect of setting extra parameters. Child processes will be automatically tracked if they're started after the crash reporter is initialized in the main process.
2. Additionally, getLastCrashReport, getUploadedReports, getUploadToServer, setUploadToServer, and getCrashesDirectory are also deprecated in the renderer process. Only addExtraParameter, removeExtraParameter and getParameters remain non-deprecated in the renderer.
3. There's a new parameter to crashReporter.start called globalExtra. Parameters passed in here will be included with any crash reported from any process, but cannot be changed after initialization. Parameters in extra or added by addExtraParameter will be included only with crashes in the process in which they're added, and they can be changed dynamically, as before. By default, the product name and app version (as reported by app.getVersion() when the crash reporter is started) are included in the global extra parameters.
4. The companyName parameter is no longer required, and further, is deprecated.

All above deprecated options will be removed in v12.x, and the majority of the crashReporter API will become main-process-only.

The reasons for making this change are as follows.

• Prior to this change, on Linux, crashReporter is incompatible with sandboxed renderers, because it must be initialized with crashReporter.start() in the renderer, but when the sandbox is engaged, crashReporter.start() cannot run on Linux. The only way to resolve this is to enable the crash reporter before the sandbox is engaged, which means before JavaScript is able to run. Thus, all the configuration must come from the main process.
• On Mac and Windows, which use crashpad, this is already how the crash reporter works, but the API does not make that clear, and in fact provides ample opportunity for misuse. In particular, for example:
  • Calling crashReporter.start() from a renderer process without having first initialized the crash reporter in the main process will not result in crashes being collected from that renderer, as crashpad won't have been initialized when the renderer was launched.
  • Most of the information passed to crashReporter.start() is ignored if the crash reporter is already enabled, including the submitURL parameter, despite it being a required parameter in the API.

Fixes #23124.

Checklist

• PR description included and stakeholders cc'd
• npm test passes
• tests are changed or added
• relevant documentation is changed or added
• PR title follows semantic commit guidelines
• PR release notes describe the change in a way relevant to app developers, and are capitalized, punctuated, and past tense.

Release Notes

Notes: crashReporter is now explicitly initialized only in the main process, and implicitly initialized in other child processes. This fixes an issue preventing the crash reporter from functioning in sandboxed renderers on Linux.