The automatic recovery uses an in-place location.replace reload, which does NOT
reliably release the OOM'd wasm heap in every browser (notably Firefox), so the
respawn can land right back in an out-of-memory state.
Add a user-gesture escape hatch to the terminal MemoryExhaustedDialog: an "Open
in a new tab" button that opens the editor in a fresh top-level browsing context
(clean retry chain) and closes the current tab. Because it runs from a real
click, window.open is not popup-blocked; window.close() may still be refused on
the original user-opened tab, which is fine — the new tab is the survivor. Copy
tells the user this sometimes helps where the in-place reload didn't.
- oom-watch.ts: export respawnInNewTab(win) — fresh-tab respawn with ?oomRetry
cleared.
- MemoryExhaustedDialog: "Open in a new tab" (primary) + "Reload this tab"
(secondary), with honest copy about Firefox + unsaved edits.
- WasmTool: wire onOpenNewTab to respawnInNewTab.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
0773acefaa