All Production Symptoms
Production Symptom5 Causal Mechanisms

Sorting 100k table rows drops the UI to 4 FPS on the main thread

Moving heavy sorting and persistence off the main thread into Dedicated Workers with Transferable TypedArrays and OPFS eliminates UI frame drops.

DevTools / RUM Signature
Long Task > 250 ms during Array.prototype.sort; structuredClone serialization spikes GC pause time

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

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

Step 2
JS RuntimeBaseline · Widely

Contiguous binary buffers (ArrayBuffer) paired with unboxed numeric views (Uint8Array, Float32Array) that transfer across workers in O(1) via ownership handoff.

Step 3
Web APIsBaseline · Widely

Origin-sandboxed virtual file system backed by raw OS files, offering synchronous in-place byte-range I/O inside Dedicated Workers.

Step 4
Web APIsBaseline · Widely

Calling a Wasm function per pixel or per DOM node burns more CPU marshaling strings across the JS boundary than running pure JS. Batch workloads into shared Linear Memory ArrayBuffers to amortize trampoline and UTF-8 copy costs.

Step 5
Web APIsBaseline · Widely

Stop freezing 60fps UI frames with Redux reducers and SQLite queries on the main thread. Isolated Worker actors serialize state mutations behind message mailboxes, keeping the main thread exclusively for DOM commits and input.

Seen in Architecture Autopsies