Does Electron crashReporter capture sandboxed renderer crashes in packaged builds

Designing crash reporting for a packaged Electron application raises uncertainty about renderer process coverage. Electron's crashReporter module can generate crash dumps for main and renderer processes when configured, and Electron 10+ uses Crashpad instead of Breakpad, which changes configuration requirements and report formats. Production builds often disable the reporter by default and require explicit setup with a company name and upload URL to function.

Sandboxing and main-process-only initialization introduce additional ambiguity. Renderer crashes may not generate reports due to sandbox restrictions or missing Crashpad configuration, and behavior differs significantly between Electron versions 8 and 11+ after the Crashpad migration. When auto-upload is disabled, dumps are stored locally, making retrieval assumptions important for diagnosis.

Does crashReporter.start() invoked in the main process enable crash capture for sandboxed renderer processes in a packaged build? Which configuration is required for local dump generation when auto-upload is disabled? When does Crashpad initialization differ between development and production packaged builds?