Runtime Segfault Tracker

Comparing memory safety across the major JavaScript runtimes.

Deno

0Last 12 Months

0All-Time Total

0Active Segfaults

0All-Time Per 1k

Bun

0Last 12 Months

0All-Time Total

0Active Segfaults

0All-Time Per 1k

Node.js

0Last 12 Months

0All-Time Total

0Active Segfaults

0All-Time Per 1k

Why Compare Segfaults?

JavaScript is a memory-safe language, but the runtimes that execute it are written in system languages like C++ (Node/Deno), Rust (Deno), and Zig (Bun). A segmentation fault (segfault) occurs when these runtimes try to access memory they shouldn't—the ultimate "hard crash" that JavaScript developers usually don't have to worry about.

By comparing these reports, we get a glimpse into the stability and memory safety of the underlying engines. While Deno leverages Rust to avoid the "billion-dollar mistake" (null pointer dereferences) in its core, all runtimes must eventually interface with low-level engines like V8 or JavaScriptCore, where manual memory management is still a reality.

How this data is collected

This dashboard queries the GitHub Search API for issues containing keywords such as segfault, sigsegv, and segmentation fault.

Last 12 Months: Total issues reported with these keywords in the past year.
All-Time Total: Total unique issues ever created matching the keywords.
Active Segfaults: Issues that are currently open and unresolved.
All-Time Per 1k: Total reports normalized per 1,000 total issues in the project.

Monthly Reports (Last 12 Months)

Note: Bun volume is significantly higher than Deno/Node.

Relative Crash Density (All-Time)

Last updated: -