All Production Symptoms
Production Symptom5 Causal Mechanisms

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.

DevTools / RUM Signature
8x duplicate wss:// connections per browser; 400 msg/s JSON.parse bursts saturate main thread at > 95% CPU

Causal 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.

Step 1
Web APIsBaseline · Widely

Origin-scoped pub/sub messaging and async mutual-exclusion locks coordinated by the browser process across tabs, iframes, and workers.

Step 2
State & ArchitectureBaseline · Widely

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.

Step 3
Web APIsBaseline · Widely

Isolated OS-thread JavaScript runtimes with their own event loop and no DOM access, communicating via structured cloning or zero-copy transferable ownership.

Step 4
Web APIsBaseline · Widely

Composable ReadableStream, WritableStream, and TransformStream pipelines that bound memory usage via highWaterMark queuing strategies and desiredSize backpressure signals.

Step 5
Network & PerformanceBaseline · Widely

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.

Seen in Architecture Autopsies