Autopsy #01: Anatomy of a Double Payment in Production
Rapid double-click or 3G network blip charges the user twice despite a disabled={isSubmitting} React button.
Cross-layer post-mortems tracing real production failures across 4 to 6 browser and framework mechanisms.
Rapid double-click or 3G network blip charges the user twice despite a disabled={isSubmitting} React button.
SPA operations dashboard climbs from 120 MB to 2.4 GB RAM over an 8-hour shift and crashes with Aw, Snap!
A single filter click freezes the UI for 180 ms INP and triggers a visible 0.14 CLS jump in the data grid.
Active tabs throw ChunkLoadError or corrupt local IndexedDB state after a production deploy.
Tooltip or modal remains trapped behind a sticky header despite z-index: 9999 while JS positioning thrashes layout.
SSR page paints instantly, flickers violently when JS boots, and wipes user input in form fields.
100% of unit and component tests pass in CI while the mobile navigation dropdown is completely unclickable in production.
A user edits a document offline on a train and silently overwrites a teammate's merged changes upon reconnection.
A card grid scrolls at 60 FPS on MacBook Pro but stutters at 11 FPS and OOM-kills the browser tab on mid-range Android.
Users opening 8 tabs exhaust realtime gateway sockets and freeze the main thread during 400 msg/s bursts.
Compromised third-party widget injects an inline script via an innerHTML sink and exfiltrates session tokens.
Rich spreadsheet and graph app drops to 4 FPS during 100k-row sorts until state and OPFS move to a Worker.
Changing a single URL filter triggers an infinite render loop, Maximum update depth exceeded, and a burst of 429 Too Many Requests responses.