Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug]: Preview tabs sometimes log "sandboxed_renderer.bundle.js script failed to run" (Electron #54149, fixed in 44.4.4)

Open Beginner friendly
  • Is something wrong?
#13,990 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
90/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
electron, typescript
Domain
desktop

Research direction

Start in apps/desktop/package.json, where the issue reports Electron 44.4.2. Check the upstream Electron release information cited in the issue, update the dependency to a fixed 44.x patch, and repeat preview_open followed by preview_snapshot to confirm the spurious sandboxed_renderer.bundle.js entries no longer appear.

Written by the indexing model from the issue text.

Description

bug upstream via-triage
Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/desktop

Steps to reproduce
  1. Open a new preview tab on any page, for example https://example.com, through preview automation (preview_open).
  2. Read the console with preview_snapshot.
  3. Repeat with new tabs; the errors appear on some of them.
Expected behavior

consoleEntries holds only the page's own messages.

Actual behavior

Some new tabs log the two errors below, and preview_snapshot returns them in consoleEntries. The page itself loads and works. For agents this is noise: an agent checking a page reads consoleEntries and has to work out that these errors are not the page's, which is misleading when the task is to find console errors.

Cause and fix

The errors come from Electron, not from the page: electron/electron#54149. When a DevTools protocol client attaches to a sandboxed frame before its first navigation finishes, the sandbox bundle runs on the initial empty document, which has no startupData. Preview automation is such a client, so the race depends on timing.

Fixed upstream in electron/electron#54155 and released in v44.4.4 ("Fixed a spurious sandboxed_renderer.bundle.js script failed to run console error when DevTools attached to a sandboxed frame before its first navigation"); backports are in v43.7.4 and v42.11.7. Bumping Electron to 44.4.5, the latest 44.x patch, should remove the errors.

Impact

Cosmetic issue

Version or commit

main @ de251fc (electron: 44.4.2 in apps/desktop/package.json); installed 0.0.43-nightly.20260926.2282

Environment

Desktop app on Linux (NixOS, Wayland, niri), Electron 44.4.2

Logs or stack traces
Electron sandboxed_renderer.bundle.js script failed to run
TypeError: Cannot destructure property 'preloadScripts' of 'binding.startupData' as it is null.
    at node:electron/js2c/sandbox_bundle:2:124925
    at ___electron_webpack_init__ (node:electron/js2c/sandbox_bundle:2:125864)
Screenshots, recordings, or supporting files

No response

Workaround

Ignore these two console entries.

Dominant language
TypeScript
Stars
23.6k
Forks
6.1k
Avg merge
8h 51m
Merged PRs (30d)
350

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pingdotgg/t3code

All issues in pingdotgg/t3code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.