Electron 43.3.0

OK so Electron 43.3.0 just dropped — August 4, 2026 — and I've been poking at it all morning. It's a patch release, so temper the hype, but there's genuinely good stuff in here. TL;DR: memory info on Linux finally tells the truth, a bunch of Windows/DPI weirdness got squashed, and Chromium got bumped again. Let's dig in.

The One New Feature

It's small but real: process.getSystemMemoryInfo() now exposes available on Linux, reading MemAvailable from /proc/meminfo. So if you've been doing hacky math to figure out how much RAM your app can actually touch — that's over. It's also backported to 42 and 44, which is nice.

The Fixes That Actually Matter

• BrowserWindow size corruption on Windows — creating a window with explicit x/y on a secondary monitor with a different DPI used to wreck the size. Fixed, and backported to 42/44.
• Dirent.parentPath in asar archives — it was undefined with withFileTypes: true in readdir/glob. If you ship a packaged app, you've probably hit this one. Fixed.
• UAF in protocol.registerStreamProtocol — a use-after-free when an error fires mid-read. That's a crash (or worse) class bug. Backported everywhere. Update.
• DevTools crash — closing DevTools while the host WebContents is being destroyed could crash. Fixed.
• requestSingleInstanceLock — certain values passed in could crash. Fixed.
• ICO files from ASAR on Windows — no more temp icon files left behind.
• Linux frameless windows — thin borders past the drop shadows when multiple windows exist. Gone.
• Linux dialogs — showOpenDialog/showSaveDialog with a bare filename defaultPath no longer opens in the void.

The Boring (But Important) Bumps

Chromium is now at 150.0.7871.212 and Node.js at v24.18.1. MV3 service worker bindings got fixed, and asar integrity errors finally name the entry that failed instead of leaving you guessing.

Verdict: it's a patch release, but the UAF fix alone is worth the upgrade. Do it.