Memory options are in Settings > Memory and in config.yaml:
memory:
lazyRestore: true
idleUnloadMinutes: 0
maxLoadedBackgroundPages: 8
lazyRestore defaults to true. On launch, ordinary inactive windows stay unloaded until selected or addressed by an agent command. Windows in background profiles continue loading on launch. Changing this option takes effect on the next launch.
maxLoadedBackgroundPages defaults to 8. Choose a limit in Settings > Memory or set an integer from 1 to 256 in the config; 0 disables the limit. Hidden pages unload in the Recent list order, oldest first, including pages in background profiles and pages with cookies or scripts. The four most recent hidden panes you have viewed stay loaded for 20 minutes after leaving them, even when the limit is below four. Visible panes do not take these four slots. Background commands do not renew this protection, and the same grace period applies to idle unloading. Visible pages, private pages, active automation, downloads, audible media, open developer tools, edited form controls, and Keep Page Loaded panes stay live, so the count can exceed the limit while those pages are protected. Unloaded pages retain their place and navigation history and reload when selected or addressed. JavaScript state is recreated on reload. This limits loaded pages; Chromium may use additional processes for browser controls, extensions, and page frames.
Headless hosts can opt into deferring background-profile panes on cold start with BMUX_LAZY_RESTORE_BACKGROUND=1. This requires lazyRestore: true; panes with Keep Page Loaded still load immediately. Persisted panes, profile cookies, automation ledgers, and cached previews stay in place. Selection or an addressed command restores a pane; agent commands still pass through the existing automation guards. Passive scripts and notifications wait until that first access. Once restored, background-profile pages continue running; this option reduces startup work and does not cap memory after activation. Foreground launches and hosts without the opt-in retain their existing behavior.
idleUnloadMinutes defaults to 0 (off). Choose 5, 15, 30, or 60 minutes in Settings to unload eligible hidden pages after inactivity. This is deliberately conservative: pages with detected scripts, forms, frames, storage, cookies, media, downloads, or active automation stay live. A page can still hold state that bmux cannot detect or restore; use this option only if reloading those pages is acceptable. Unloaded pages remain in the layout and wake on selection or agent access.
Linux hosts with a small /dev/shm can set BMUX_DISK_SHARED_MEMORY=1 before launch to use Chromium's disk-backed shared-memory path. Use a disk-backed /tmp for this option. It takes effect when the host starts.
Open profile settings and select the Pane tab to toggle “Keep Page Loaded” for a pane that must retain its in-memory state. Protected panes load on launch and are exempt from idle unloading. Agents can set the same persistent flag with bmux pane keep-alive -t PANE --enabled, or with the pane.keep-alive RPC and { "pane": "pane_id", "enabled": true }. Use --enabled=false to clear it. Idle unloading restores navigation history and scroll position when Electron can recover them, but does not preserve arbitrary JavaScript state.
Each pane now owns exactly one page, and pane IDs address that page. Existing state files are upgraded on launch: the formerly active page stays in its pane; any additional hidden pages become separate windows in the same session. The original state is saved as state.json.v1-backup, and the migrated pane IDs persist immediately. Legacy tab.* RPC calls are accepted during migration, but they no longer create or select hidden pages inside a pane. New integrations should use pane IDs and list-panes.
Run bmux memory for a fresh JSON snapshot, or bmux memory --history to also
include up to 120 samples collected every 30 seconds since startup (about one
hour). RPC equivalents are memory and memory with { "history": true }.
History stays in memory and clears when the app exits. Requests do not add to
history, so frequent polling cannot displace the periodic samples.
current.processes is sorted by working-set bytes, largest first. Each row has
its PID, creation time, type, associated WebContents, pane IDs, and profile IDs.
current.panes maps these to session and window IDs and reports whether
the page is visible, background-throttled, or has queued automation (busy).
current.contents includes browser UI and extension WebContents as well as page WebContents.
Main-frame and subframe processes are mapped where Electron exposes them.
Profiles list their associated processes and the sum of their working sets.
Use existing pane/session/profile list commands to resolve the stable IDs.
deltaBytes compares the current measurement with the previous periodic sample,
whose timestamp is comparedTo. A new process has a null delta; PID reuse is
detected using process creation time. The total delta includes process creation
and exit. Sustained growth in the same process with a stable page count warrants
investigation, but does not by itself prove a leak.
Each process is counted once in totalWorkingSetBytes. Panes sharing a renderer
list the same PID; do not count that process separately for each pane. Profile
totals can overlap if a process maps to more than one profile, and exclude
processes without mapped panes. Browser, GPU, utility, and unmapped processes are
still included in the overall total. Frame ownership is best effort during
navigation or process exit.
Electron reports working sets in kilobytes; the command converts them to bytes. Working sets include shared resident pages. Their sum is not the same metric as macOS Activity Monitor's memory footprint, especially with memory compression. See Electron's process metrics and memory information.
Sampling does not execute page JavaScript, capture screenshots, focus windows, change selection, or change throttling. Reports omit URLs, titles, page content, and credentials. This feature measures memory; it does not unload pages.