Affected version
Reports that share this version, grouped in one feed.
Next.js App Router navigation fails with React error #412 when receiving partial RSC payloads during PPR, causing client-side crash instead of falling back to full page load.
Next.js's createPrerenderInterruptedError creates a plain Error whose lazy stack accessor retains captured V8 call site frames until .stack is read. When that Error is used as AbortSignal.reason, any retained AbortSignal transitively pins the entire rendered page (html, segmentData, buffers, promises) via the frames' closures and contexts. Measured retention is ~1,756 KiB per signal, versus ~1 KiB when frames are stripped. The defect is latent: Next collects these signals normally, but userland/instrumentation commonly retains signals, turning a small leak into multi-GB memory pressure.
LangChain, LlamaIndex, and Pydantic
Pinecone, Chroma, Weaviate, Qdrant, and neighboring stores
Next.js, Supabase, and the surrounding app stack