Native Crash Reporting with Minidumps

A developer comparing a crashed native application with its stacktrace

Minidump support is no longer an experimental feature as of Bugsink 2.6.2.

The feature is based on minidumps: small binary reports written when a native application crashes. A minidump records the state of the crashed process, including its threads, loaded modules, crash reason, operating system, and CPU architecture.

With the debug information from the exact build that crashed, Bugsink turns the addresses in that dump into a readable stacktrace with function names, filenames, line numbers, and nearby source code. That makes a hard native crash debuggable in much the same way as an ordinary exception in Bugsink.

From proof of concept to production

Bugsink has had some support for minidumps for quite a while. Back in November 2025, a large prospective customer asked whether Bugsink could handle them. I built a proof of concept that turned crash dumps into readable stacktraces, and it shipped in Bugsink 2.0.7.

Because the large prospect never materialized into a paying customer, the work never really made it past PoC-status. It contained a few known DOS-related security issues and was gated behind a feature flag, disabled by default. A large or malicious upload could still consume far too many resources. It was a proof of concept from the beginning, and the flag kept that unfinished work out of normal installations.

Another customer request, in October 2026, prompted the next phase. This customer wanted to use minidumps on managed Bugsink. Before enabling it for them, we needed to address the risk that a single upload could take down the service.

So, we tightened upload limits, limited source extraction, and stopped crash processing from holding up other database writes. With those changes in Bugsink 2.6.2, we could finally enable minidumps on managed Bugsink.

In November, 2.6.3 replaced the C++ minidump stack walker with Rust. That’s part of our broader effort to reduce C and C++ dependencies after the Brotli security issues.

Enabling minidumps

Managed Bugsink already has minidumps enabled. Self-hosted installations still need:

FEATURE_MINIDUMPS=True

The setting will become the default in Bugsink 2.7. We’re keeping 2.6 opt-in rather than changing a default involving much larger uploads in a patch release.

How it works

Two things have to reach Bugsink:

  • The application uploads a minidump when it crashes. Crashpad can take care of creating, storing, and sending it.
  • The build uploads its debug files using sentry-cli, optionally including the source files for context lines.

Both contain the same debug ID, which lets Bugsink match the crash to the exact build. There is no guessing based on a release name or filename.

For an application that already uses sentry-native with Crashpad, the application-side change is the DSN: point it at your Bugsink project. Crashpad still captures and sends the crash; Bugsink receives it and turns it into an issue. For a direct Crashpad or Breakpad integration, configure the uploader to send the dump to Bugsink’s minidump endpoint.

Your build pipeline needs to upload the matching debug files before sending crashes from that build. Bugsink resolves the stacktrace when the crash arrives, so uploading symbols afterwards won’t repair an existing event. Include source files in the upload if you also want to see the code around each frame.

The setup guide for existing crash reporters shows the upload URL and commands. For framework SDKs, check the compatibility notes first: support depends on what the SDK sends, and not every native crash format is a minidump.

What’s tested

Our end-to-end test used sentry-native with Crashpad on Linux x86-64, including debug-file and source uploads. It verified that a crash reaches Bugsink with function names, filenames, line numbers, and source context.

That doesn’t establish that every SDK and platform combination works. The minidump documentation separates supported formats from tested integrations and lists the current limitations.

Bugsink 2.6.3 was already out when this article was published. Minidump support became ready for real use in 2.6.2.