Garbage collection pauses under 50ms

A GC pause of 250ms during a scroll or animation freezes the frame pipeline: no input events are processed, no pixels are painted. Users experience this as a sudden hard stutter that is qualitatively worse than slow load times. ISO 25010:2011 time-behaviour captures the latency; the GC pressure that produces long pauses is typically caused by allocating large arrays or objects inside render loops or scroll handlers — code patterns that generate garbage faster than incremental GC can collect it.

Move expensive computations out of render loops using useMemo or useCallback. For server-side Node.js services, use clinic.js to identify GC pressure hotspots.

// components/dashboard.tsx — memoize to reduce GC pressure in render
const processedRows = useMemo(
  () => rawData.map((row) => transformRow(row)),  // runs once per rawData change
  [rawData]
)

For scroll handlers, avoid creating new arrays or objects inside the callback — pre-allocate or reuse structures.