symbolicate-crash-dump

Install electron-minidump globally via npm, then run electron-minidump crash-file.dmp to generate a backtrace. If frames lack method names, download the matching symbol zip for your build and copy the .sym files into the electron-minidump breakpad_symbols cache, then re-run.

Insiders and Stable builds use symbol zips from the private microsoft/vscode-electron-prebuilt releases, downloaded with an authenticated GitHub CLI. Code - OSS builds use public symbols from electron/electron releases. Match by Electron version, quality, platform, and architecture.

No, electron-minidump does not run on Windows; a macOS or Linux device is required to perform symbolication. However, you can symbolicate dumps produced by Windows builds as long as you run the tool on macOS or Linux.

Breakpad matches symbols by exact debug-id, not version name, so the .sym file hash must exactly match what the cache directory expects. Some modules like runtime.node and third-party DLLs have no public symbols at all and cannot be symbolicated.

Run strings on the dump and grep for markers like --type=renderer, --type=gpu-process, or node.mojom.NodeService. The NodeService utility marker indicates the extension host, since modern Electron runs it inside a Node utility process.

Remote server extension host crashes use core dumps and gdb instead of electron-minidump. Enable core dumps with ulimit -c unlimited, retrieve the core via coredumpctl, then load it with gdb against the server's node binary and run bt full.