denoland/deno · critical

Failed to initialize a JsRuntime: {}

Error message

Failed to initialize a JsRuntime: {}

What it means

JsRuntime::new is the panicking convenience constructor: it calls try_new and, on error, panics with "Failed to initialize a JsRuntime" plus the full cause chain via err.print_with_cause(). Construction can fail while allocating the V8 isolate, deserializing the startup snapshot (including extension snapshot-state mismatches), running extension initialization, or when the process is out of resources (memory, threads, file descriptors). The panic is only a wrapper; the real cause is in the printed error chain.

Source

Thrown at libs/core/runtime/jsruntime.rs:743

  /// The `expose_natives` flag is used to expose the v8 natives
  /// (eg: %OptimizeFunctionOnNextCall) and GC control functions (`gc()`).
  /// WARNING: This should not be used for production code as
  /// this may expose the runtime to security vulnerabilities.
  #[cfg(any(test, feature = "unsafe_runtime_options"))]
  pub fn init_platform(
    v8_platform: Option<v8::SharedRef<v8::Platform>>,
    expose_natives: bool,
  ) {
    setup::init_v8(v8_platform, cfg!(test), expose_natives);
  }

  /// Only constructor, configuration is done through `options`.
  /// Panics if the runtime cannot be initialized.
  pub fn new(options: RuntimeOptions) -> JsRuntime {
    match Self::try_new(options) {
      Ok(runtime) => runtime,
      Err(err) => {
        panic!(
          "Failed to initialize a JsRuntime: {}",
          err.print_with_cause()
        );
      }
    }
  }

  /// Only constructor, configuration is done through `options`.
  /// Returns an error if the runtime cannot be initialized.
  pub fn try_new(mut options: RuntimeOptions) -> Result<JsRuntime, CoreError> {
    let _t0 = startup_phase_begin();
    setup::init_v8(
      options.v8_platform.take(),
      cfg!(test),
      options.unsafe_expose_natives_and_gc(),
    );
    startup_phase_end(_t0, "init_v8");
    JsRuntime::new_inner(options, false)

View on GitHub (pinned to 336da420f4)

Solutions

1. Switch to JsRuntime::try_new(options) and inspect the returned CoreError chain to find the actual failing stage
2. Regenerate the startup snapshot with the exact deno_core and extension set of the consuming binary
3. Check resource limits (cgroup memory, RLIMIT_NOFILE, thread count) when the cause is isolate allocation
4. Reduce the number of simultaneously alive runtimes, or construct them lazily

Example fix

// before
let runtime = JsRuntime::new(options); // panics on any init failure

// after
let runtime = match JsRuntime::try_new(options) {
  Ok(rt) => rt,
  Err(err) => {
    eprintln!("runtime init failed: {}", err.print_with_cause());
    return Err(err.into());
  }
};

// Before constructing, confirm the snapshot blob is present and was built for
// this build (embed a version marker next to the blob at build time).
assert_eq!(SNAPSHOT_LAYOUT_TAG, env!("DENO_CORE_LAYOUT_TAG"),
  "startup snapshot does not match this binary");

// Use the fallible constructor and branch on the cause chain.
let runtime = match JsRuntime::try_new(options) {
  Ok(rt) => rt,
  Err(err) => {
    log::error!("JsRuntime init failed: {}", err.print_with_cause());
    return Err(MyError::RuntimeInit(err));
  }
};

When it happens

Trigger: JsRuntime::new with a startup snapshot built by a mismatched deno_core/extension set; an extension failing its init JS or state deserialization; V8 isolate allocation failing under memory cgroups, thread limits, or RLIMIT_NOFILE exhaustion; embedding many concurrently alive runtimes.

Common situations: Upgrading deno_core/deno_runtime and reusing an old snapshot blob; containers with low memory limits where the first runtime boot OOMs; test harnesses spawning dozens of runtimes in parallel; corrupted snapshot files (truncated build artifacts, bad cargo caching).

Related errors

• {path} exists
• unable to convert
• Failed to initialize JsRuntime for snapshotting: {:?}
• Attempted to read snapshot data out of range: {id} (of {})
• Attempted to read the snapshot data at index {id} twice

AI-assisted analysis of denoland/deno@336da420f4 (2026-08-20). Data as JSON: /api/errors/6f1a9e9ad875beac. Report an issue: GitHub.