Opening multiple tabs exhausts WebSocket limits and freezes UI
Without cross-tab leader election and Worker-offloaded stream backpressure, every open tab duplicates realtime sockets and main-thread parsing.
8x duplicate wss:// connections per browser; 400 msg/s JSON.parse bursts saturate main thread at > 95% CPUCausal Chain of Browser Mechanisms
Ordered from trigger to root invariant. Open any mechanism to inspect its internals or reproduce the behavior in an interactive lab.
Origin-scoped pub/sub messaging and async mutual-exclusion locks coordinated by the browser process across tabs, iframes, and workers.
Stops N open browser tabs from hammering WebSockets, refreshing OAuth tokens in parallel, and corrupting IndexedDB by electing a single leader tab with Web Locks and BroadcastChannel.
Isolated OS-thread JavaScript runtimes with their own event loop and no DOM access, communicating via structured cloning or zero-copy transferable ownership.
Composable ReadableStream, WritableStream, and TransformStream pipelines that bound memory usage via highWaterMark queuing strategies and desiredSize backpressure signals.
Unbounded WebSocket bursts spike tab memory until OOM, while synchronized reconnects DDoS your own edge servers. Pair ReadableStream backpressure with full-jitter exponential backoff so slow UI consumers throttle sockets safely.