Preview: Electron 43 releases with Chromium 150 and key fixes

platform version release preview infographic

platform version release preview: the ugliest Electron bugs aren’t flashy — they’re the ones where prod runs “successfully” while executing the wrong code.

If you ship sandboxed preloads or depend on webContents.debugger for QA/telemetry, Electron 43.0.0 is shaping up to be one of those releases where the top risk is silent misbehavior: stale cached bytecode and missing network visibility. That’s the kind of failure mode that turns an incident review into a blame-fest.

Stable is scheduled for 2026-06-30. Betas are already out, with Chromium 150, V8 15.0.223, and Node 24.16.0 in the line.

Sandboxed preload cache: fixed the “same-length edit” time bomb

Electron v43 betas include a fix for sandboxed preload scripts running a stale cached version after the script was modified without changing its file size. The fix is in PR #51932.

What actually happened: V8’s CachedData source validation was effectively checking length only. Edit your preload bundle, keep byte-length identical (not hard with minified output), and Electron could happily reuse old cached bytecode. You deploy a hotfix, and the app keeps running yesterday’s preload. No crash. No warning. Just wrong behavior.

Electron’s fix binds cache entries to a SHA-256 of the preload source, so the cache only serves a blob whose hash matches the bytes it just read. That’s boring engineering. Also exactly what you want.

So what for your workflow: if you use hot reload for preloads (or any build step that can produce same-size output), add a test that edits the preload while preserving length and asserts new behavior. Otherwise you’ll waste hours chasing “why didn’t my fix work?” ghosts.

Frameless windows: win.center() regressions get patched

Electron v43 beta.3 includes PR #51920, fixing frameless windows shrinking when calling win.center() on Linux/Windows, plus a Windows off-center issue.

So what: frameless windows are already a swamp of DPI scaling, window manager quirks, and custom drag regions. If your app shipped workarounds (manual bounds math, delayed center calls, DPI fudge factors), v43 might make those workarounds harmful. Run your geometry regression suite. Especially on Windows with mixed-DPI monitors.

DevTools/CDP: Network panel data loss when attaching webContents.debugger

Electron v43 beta.4 calls out a fix for DevTools Network panel missing most requests after navigation when webContents.debugger is attached (PR #51964).

So what: anyone doing “attach CDP, drive the app, scrape network events” (QA harnesses, synthetic monitoring, in-house tooling) can get misleadingly empty results. If you rely on CDP signals for pass/fail gates, pin at least beta.4 when testing v43.

Electron releases keep looking like “Chromium did a thing,” because… Chromium did a thing. The real story in v43 is operational: the project is paying down sharp edges that cause silent correctness failures.

The preload cache bug is the archetype of 2 AM pain: the app “updated,” but behavior didn’t change. Teams blame CDN propagation, auto-updater race conditions, flaky CI artifacts — anything except a bytecode cache keyed on length. Fixing it with content hashing is an admission that the prior trust boundary was wrong.

Meanwhile, the CDP/DevTools issue is about observability integrity. When your debugging surface lies, engineers make bad decisions. That’s how outages get longer.

Try the v43 beta (recommended for preview testing):

npm i -D electron@43.0.0-beta.4
# or
npm i -D electron@beta

Yarn:

yarn add -D electron@43.0.0-beta.4

Red flags to watch for in logs / behavior:

Preload weirdness: your preload logs don’t match the source you think shipped; changes “don’t take.” Suspect stale bytecode cache behavior if you’re on earlier betas, or if your tooling does same-length edits.
Frameless geometry: windows that shrink after center, off-by-one bounds, titlebar hit-testing drift on DPI changes.
CDP/DevTools observability: missing network requests after navigation when debugger is attached; QA scripts that suddenly see “no requests” and fail.

Practical advice: test on Windows first. Frameless + DPI + sandbox is where Electron apps go to die.