Diagnostic Index · 25 Production Symptoms

Production Symptoms & DevTools Signatures

Start from the error message, layout glitch, or Web Vitals regression you observe in production and trace the causal chain of browser mechanisms behind it.

4 concepts1 autopsy
My z-index: 9999 is ignored behind a sticky header

A parent with transform, opacity < 1, will-change, or filter creates an isolated stacking context that traps child z-index values inside its subtree.

Computed z-index: 9999, yet element paints underneath sibling with z-index: 10 (isolated stacking context via transform/opacity/filter)
4 concepts1 autopsy
Scrolling stutters at 11 FPS on mobile and kills the tab

Animating layout properties or over-promoting cards with will-change saturates mobile VRAM and forces main-thread rasterization on every scroll tick.

DevTools Layers panel > 400 MB GPU memory; Performance trace shows Paint + Composite Layers > 35 ms per frame
3 concepts
An async loop freezes the browser main thread completely

Unbounded Promise/microtask chains starve the rendering step between macrotasks and block all user input until the microtask queue drains.

Long Task > 5000 ms; DevTools Performance shows continuous Microtask Checkpoint draining with zero Paint frames
3 concepts1 autopsy
UI updates trigger full-page forced synchronous reflows

Interleaving DOM style writes with geometric reads such as offsetHeight or getBoundingClientRect forces synchronous Blink layout recalculations.

DevTools Performance warning: "Forced reflow is a likely performance bottleneck" inside Recalculate Style + Layout
3 concepts1 autopsy
Browser Back button reloads the entire page from scratch

Attaching unload listeners, sending Cache-Control: no-store, or holding open IndexedDB locks disqualifies the page from instant Back/Forward Cache snapshots.

DevTools Application > Back/forward cache: NotRestoredReasons = ["unload-handler"] or Cache-Control: no-store
3 concepts1 autopsy
Click handler fires on the wrong element or misses Shadow DOM target

Capture, bubbling, and Shadow DOM event retargeting alter event.target versus event.currentTarget along the composed path.

event.target !== event.currentTarget; Shadow DOM event.target retargeted to host element outside shadow root
5 concepts1 autopsy
Rapid double-click charges the user twice despite disabled button

Asynchronous React state updates lag behind synchronous DOM click dispatch, allowing duplicate mutations unless guarded by state machines and idempotency keys.

Network tab shows 2 concurrent POST /checkout requests within 12 ms before React state flush disables the submit button
5 concepts1 autopsy
SPA dashboard climbs to 2.4 GB RAM and crashes with Aw, Snap!

Long-lived event listeners, uncleaned MutationObservers, and stale hook closures retain detached DOM subtrees across route transitions until V8 hits the heap limit.

DevTools Memory Heap Snapshot shows growing Detached HTMLDivElement retainers and uncancelled AbortController/Observer closures
5 concepts1 autopsy
Single filter click freezes UI for 180+ ms INP with visible CLS jump

Cascading custom property invalidations and synchronous Virtual DOM reconciliation combine with layout thrashing to blow past the 200 ms INP budget.

Web Vitals INP > 200 ms (Processing Duration > 140 ms) + CLS > 0.1 during synchronous state commit and layout read
4 concepts1 autopsy
ChunkLoadError or corrupt IndexedDB state after a production deploy

Cached HTML shells or waiting Service Workers reference old hashed JS chunks removed on the CDN, breaking lazy imports and client schema expectations.

Uncaught ChunkLoadError: Loading chunk 42 failed (404) / Failed to fetch dynamically imported module
5 concepts1 autopsy
SSR page flickers on load and wipes typed text in form inputs

Divergent server/client trees trigger React hydration bailout, discarding SSR DOM nodes and resetting any user input entered before JS finished booting.

Warning: Text content did not match. Server vs Client / Hydration failed because the initial UI does not match what was rendered on the server
5 concepts1 autopsy
100% of unit tests pass in JSDOM while mobile dropdown fails in prod

JSDOM stubs layout geometry, passive touch listeners, and compositor hit-testing, masking real browser failures until tested in an actual engine.

Vitest/Jest JSDOM suite green; Safari/Chrome mobile throws Unable to preventDefault inside passive event listener or misses hit-testing
4 concepts1 autopsy
Offline edit silently overwrites teammate changes on reconnect

Naive offline mutation replay without causal vector clocks, CRDTs, or cross-tab Web Locks clobbers concurrent edits once connectivity returns.

IndexedDB VersionChange / Last-Write-Wins PUT overwrites server revision without conflict detection or CRDT merge
5 concepts1 autopsy
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% CPU
5 concepts1 autopsy
Third-party script injects inline XSS via innerHTML sink

Unsanitized DOM sinks and prototype pollution allow compromised third-party widgets to execute arbitrary scripts unless locked down by Trusted Types and strict CSP.

SecurityPolicyViolation / TypeError: This document requires TrustedHTML assignment on Element.innerHTML
5 concepts1 autopsy
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.

Long Task > 250 ms during Array.prototype.sort; structuredClone serialization spikes GC pause time
3 concepts
Web font swap causes sudden text jump and high CLS score

Late-discovered web fonts with mismatched metric overrides resize line boxes when swapping in, causing measurable Cumulative Layout Shift.

Web Vitals CLS > 0.1; Performance Layout Shift record attributed to @font-face swap from fallback sans-serif
3 concepts
API request fails with CORS preflight OPTIONS 403 or missing header

Non-simple headers or methods trigger a mandatory OPTIONS preflight that fails when the server omits Access-Control-Allow-* or mishandles credentials.

Access to fetch at ... has been blocked by CORS policy: Response to preflight request does not pass access control check
3 concepts
Async callback or interval reads stale React state after update

Closures capture the lexical environment of the render in which they were created, reading outdated bindings when effects omit dependencies or refs.

Logged state value inside setInterval/addEventListener stays stuck at initial render value despite subsequent setState calls
3 concepts
height: 100vh overflows behind mobile browser address bar

Classic 100vh maps to the large viewport height, extending under retracting mobile toolbars unless replaced with dvh or svh units.

Fixed bottom CTA clipped below mobile Safari/Chrome dynamic toolbar when layout viewport differs from visual viewport
4 concepts1 autopsy
Keyboard Tab focus escapes modal dialog into background page

Custom div modals fail to mark background subtrees inert or use the native Top Layer, allowing keyboard focus and assistive tech to leak behind the backdrop.

document.activeElement moves behind modal overlay; screen reader navigates background landmarks while dialog is open
3 concepts
Validation regex hangs the browser tab on crafted user input (ReDoS)

Nested quantifiers in NFA regular expressions cause exponential backtracking on near-matching strings, locking up the JS thread.

Main thread frozen 100% inside RegExp.prototype.test; DevTools Flame Chart shows catastrophic backtracking
3 concepts
Utility CSS classes fail to override component styles despite source order

Unlayered compound selectors outrank later single-class utilities in the cascade unless isolated with @layer declarations.

DevTools Styles pane shows utility rule crossed out due to higher selector specificity (0,2,0) vs (0,1,0)
3 concepts1 autopsy
Users remain stuck on old app version after deploy due to Service Worker

A new Service Worker waits until all controlled tabs close unless skipWaiting and client reload coordination are handled cleanly.

DevTools Application > Service Workers shows new worker stuck in "waiting to activate" while tabs serve cached old bundle
5 concepts1 autopsy
useEffect dependency loop triggers Maximum update depth exceeded and 429 API burst

Allocating a fresh filter object literal per render fails Object.is() in useEffect, rescheduling commits and uncancelled fetches until API rate limits trip.

Console: "Maximum update depth exceeded"; Network waterfall shows 47+ uncancelled GET /api/items requests returning HTTP 429 Too Many Requests