Aquesta és una versió anterior. La versió actual és la 4.10.0. wmux 4.10.0 · Data de publicació:
Fitxers d’instal·lació 3.30.0
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | EXE | Usuari actual | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
Added
- A browser pane's CDP target is registered as soon as the guest attaches, instead of only after the page finishes loading, so automation can reach a pane whose page is slow or unreachable. Two related fixes: an already-attached debugger no longer aborts registration outright (the guard never matched Electron's actual error text), which previously left a reloaded guest permanently unregistered. (#517)
- Discard hidden browsers (opt-in) — lightweight mode now has a memory lever. Lightweight mode only capped CPU; every hidden browser pane still held its full Chromium renderer in memory. A new sub-toggle under "Lightweight background browsers" ("Discard hidden browsers", default off) unloads a browser pane after it stays invisible for 5 minutes — the guest renderer process exits and its memory is reclaimed, and the pane shows a small "suspended" placeholder. Returning to the pane (or navigating it) reloads the page; scroll position and unsaved form input are lost, which is why it's opt-in and the dwell is generous. Panes playing audio are never discarded, and automation (MCP tools, screenshots) targeting a discarded pane wakes it automatically and waits for the reload before running — so background agent flows keep working. (#517)
- Lightweight mode for built-in browsers (opt-in). With many workspaces open, every embedded browser pane kept its Chromium renderer running full-speed even when its workspace was hidden — that CPU was burned on purpose so background automation (MCP screenshots, evaluate) never stalled. A new Settings → Terminal toggle ("Lightweight background browsers", default off) CPU-throttles a browser guest only while it is effectively invisible — hidden workspace, pane hidden behind another pane's zoom, unselected tab, or minimized window — and any automation touching a guest takes a short-lived lease that runs it full-speed for the duration, so background automation stays correct. (Classic background-tab timer throttling turned out to be inert for these guests — Electron keeps a CSS-hidden webview in the "visible" page state — so the throttle is applied as a CDP CPU-rate override, measured at a 2–5× CPU reduction on timer-driven pages.) This reclaims CPU only; renderer memory is unchanged. (#517)
What's Changed
- Lightweight mode for built-in browsers: CPU-throttle invisible guests (opt-in) by @openwong2kim in #528
- Discard long-hidden browser panes to reclaim memory by @openwong2kim in #530
- chore(release): 3.30.0 by @openwong2kim in #532
Full Changelog: v3.29.0...v3.30.0
