Skip to content

Windows nightly update leaves V8 startup files missing in 0.1.8 #31513

Closed

Description

@matthewvanderbijl

What happened

T3 Code Nightly stopped opening after an in-app update on November 5, 2026. Repeated launches exited immediately without showing a window. Rerunning the cached installer for the same version restored the missing startup files and allowed the app to open.

Diagnosis

The installed desktop executable reported 0.1.8-nightly.20261105.4218. Before repair, snapshot_blob.bin and v8_context_snapshot.bin were missing. Launch attempts repeatedly logged a fatal V8 startup snapshot error; one observed launch exited with code -2147483645.

The desktop trace records quitAndInstall at 15:38:09 SAST (13:38:09 UTC) on November 5. The matching release's updater delegates to Electron's quitAndInstall; a successful handoff trace does not establish successful installer completion.

The evidence is consistent with an incomplete installation. The reason the files were left missing is unconfirmed. This appears to be a recurrence of #27486 on a newer nightly; no separate root cause has been established.

Steps to reproduce

No deterministic reproduction was found. The observed sequence was:

  1. Apply an in-app update to T3 Code Nightly on Windows with a WSL2 backend.
  2. Attempt to reopen the desktop app after the update.
  3. Observe no window and immediate termination on repeated launches, with the V8 startup snapshot error.
  4. Rerun the cached installer for the same version; verify that the startup files return and the app opens.

Version

Desktop: 0.1.8-nightly.20261105.4218, verified from the installed executable. The separate npx t3 triage CLI reported 0.0.44.

Environment

Windows x64, build 26200, with a WSL2 Ubuntu backend. Nightly desktop channel.

Evidence

Desktop trace: 2026-11-05 15:38:09 SAST — quitAndInstall

Repeated launch error:
FATAL:gin\v8_initializer.cc:675] Error loading V8 startup snapshot file

One observed launch exit code: -2147483645

Before repair:
snapshot_blob.bin         missing
v8_context_snapshot.bin   missing

After rerunning the same-version cached installer:
snapshot_blob.bin         present
v8_context_snapshot.bin   present
Desktop window opened and responded.
Backend reported the matching version.

Related issues

#27486 reports the same missing V8 startup files after a Windows update on an older nightly. This report records a likely recurrence on 0.1.8-nightly.20261105.4218, with no claim of a distinct root cause.

Fix applied or workaround

Reran the cached installer for 0.1.8-nightly.20261105.4218 with /S. It completed successfully, restored both startup snapshot files, and the desktop app opened with a responding window. The backend also reported the matching version.

Suggested investigation: installer extraction diagnostics and validation that required startup files exist after extraction. The app fails during V8 initialization, before application-level recovery can run.

Filed by

Codex (GPT-6) via t3 triage. The triage CLI generated its machine report; its nested agent could not start without an interactive terminal, so the investigation was completed in the existing Codex session.

Activity

  1. juliusmarminge commented on Nov 5, 2026

    @juliusmarminge
    Member

    Duplicate of #27486: same symptom on the same surface. A Windows in-app (NSIS) update leaves v8_context_snapshot.bin and snapshot_blob.bin missing, and every launch then fails with Error loading V8 startup snapshot file.

    Checked against main at 337c585: #27486 is still open, and no change merged since 0.1.6 validates or recovers a partially extracted Windows install. Its open fix, #27526, guards one known cause (the installer running out of disk space). The cause on your machine is unconfirmed, as you noted, so tracking stays on https://git.cafe/pingdotgg/t3code/issues/27486. Your 0.1.8 recurrence data point (0.1.8-nightly.20261105.4218, quitAndInstall at 13:38:09 UTC, a same-version reinstall with /S restoring both files) is useful there. If you can, add free space on the install and %TEMP% volumes at update time, and whether you launched the app manually before the installer finished.

    Closing as a duplicate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions