Updated Oct 19, 2026

Utilities

Symbolicate a Linux Electron crash dump

electron-minidump is an offline Linux x86_64 Electron minidump symbolication node.

Agent

overview

What electron-minidump does

Supply dump.dmp and matching Breakpad symbols to receive a native backtrace and provenance report.

The packaged Electron driver uses its native stack walker and a fresh local symbol cache. Supplied symbol MODULE debug identifiers must match dump modules. Missing symbols remain explicitly unresolved; no symbol-server downloads or dump executable execution occur.

Supply 1 to 10 Linux x86_64 .sym files: 16 MiB each and 32 MiB total, with a dump at most 20 MiB. Symlinks are refused. Native metadata has 15 seconds and symbolication 45 seconds; other platforms and automatic symbol acquisition are outside scope.

The packaged driver is electron-minidump 3.2.2 with native minidump 0.23.0. Retained notices cover the ISC driver, MIT native wrapper and BSD-style Breakpad components. The linked source identifies the driver used by this node.

source github.com/nornagon/electron-minidump

use cases

Where electron-minidump fits

Resolve matching crash frames

Resolve frames where supplied symbol identifiers match dump modules.

Inspect missing-symbol modules

See which modules lack supplied symbols and remain unresolved.

Keep native stackwalk provenance

Keep the original stackwalk text with adapter provenance metadata.

reference

electron-minidump inputs and flags

1 inputs
NameTypeFlagDescription
sourceFOLDER--sourceFolder with dump.dmp (MDMP header, up to 20 MiB) and symbols/ containing 1-10 matching Linux x86_64 .sym files, 16 MiB/file, 32 MiB total. Symbol MODULE debug IDs must match dump modules. Symlinks refused. Fixed native CLI, no force/download mode; unmatched modules reported unresolved. Native metadata timeout 15s and stackwalk 45s. No dump executable is launched.

Showing key inputs. electron-minidump exposes 1 inputs in total.

example

Run electron-minidump

electron-minidump · command
node /app/run.mjs --source ./source ./output

guidance

Choosing electron-minidump

Use this operation when a Linux x86_64 dump and genuine matching symbols are already available. It cannot recover absent symbols or promise every stack frame will resolve.

faq

electron-minidump questions

source: Folder with dump.dmp (MDMP header, up to 20 MiB) and symbols/ containing 1-10 matching Linux x86_64 .sym files, 16 MiB/file, 32 MiB total. Symbol MODULE debug IDs must match dump modules. Symlinks refused. Fixed native CLI, no force/download mode; unmatched modules reported unresolved. Native metadata timeout 15s and stackwalk 45s. No dump executable is launched.

Backtrace and provenance report. The packaged Electron driver uses its native stack walker and a fresh local symbol cache. Supplied symbol MODULE debug identifiers must match dump modules. Missing symbols remain explicitly unresolved; no symbol-server downloads or dump executable execution occur.

Supply 1 to 10 Linux x86_64 .sym files: 16 MiB each and 32 MiB total, with a dump at most 20 MiB. Symlinks are refused. Native metadata has 15 seconds and symbolication 45 seconds; other platforms and automatic symbol acquisition are outside scope.

Use this operation when a Linux x86_64 dump and genuine matching symbols are already available. It cannot recover absent symbols or promise every stack frame will resolve.

The public image repository includes download instructions for this version and a separate source/notices bundle. Its overview provides an immutable ORAS command, the expected bundle checksum and pinned upstream source directions. The bundle contains the original build recipe, runtime sources and retained component license notices. Image, source and license notice downloads.

Run electron-minidump yourself

The saved synthetic native check resolved the Electron Crash function at atom_bindings.cc:27 from an upstream Linux fixture and genuine matching symbols. It reported 180 modules without supplied symbols and no network symbol downloads. This is a verified result summary, not a complete backtrace sample. The command shows the container entrypoint with example paths.

Facts on this page come from the live Trickest tool library.