Note
π€ GPT-6 responding on behalf of matthewvanderbijl
Adding the newer-nightly recurrence from #31513 here, as requested by @juliusmarminge.
- Version/environment:
0.1.8-nightly.20261105.4218, Windows x64 build26200, WSL2 Ubuntu backend. - Update timeline:
ElectronUpdater.quitAndInstallstarted at 2026-11-05 13:38:09 UTC (15:38:09 SAST). The installed app'sdebug.logfirst records the V8 error at 15:38:39.550 SAST, approximately 30 seconds later, with repeated failures afterward. - Failure and recovery:
snapshot_blob.binandv8_context_snapshot.binwere missing. Rerunning the cached installer for the same version with/Srestored both files and produced a responding desktop window; the backend reported the matching version.
| 1 | [1105/153839.550:FATAL:gin\v8_initializer.cc:675] Error loading V8 startup snapshot file |
| 2 | [1105/153839.577:FATAL:gin\v8_initializer.cc:675] Error loading V8 startup snapshot file |
| 3 | [1105/155222.493:FATAL:gin\v8_initializer.cc:675] Error loading V8 startup snapshot file |
For the two requested follow-up details:
- Install and TEMP volume space: Both
%LOCALAPPDATA%\Programs\t3codeand the effective Windows%TEMP%directory resolve to C:. At 2026-11-05 15:09:49 UTC, after the repair, Windows reported 928,239,616 bytes free (about 885 MiB / 0.86 GiB) on that volume. No update-time free-space measurement was recovered. This later measurement makes low space worth investigating, but does not establish how much space was available during extraction or prove the cause. - Launch before installer completion: The logs establish a failed launch approximately 30 seconds after the updater handoff, but do not identify whether it was an automatic restart or a manual launch, or establish whether the installer was still running. Later manual launch attempts were made while troubleshooting. A manual launch during extraction remains unconfirmed.
The underlying reason extraction left these files missing is still unconfirmed; this evidence should be tracked as a recurrence of this issue.