[Node.js builds/tests (tsc, webpack, next build, jest) in CI/containers] 'FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory' / 'Ineffective mark-compacts near heap lim…

Cause (Documented platform behavior): Workload exceeds the configured/default V8 heap limit (or a memory leak). Fix status: documented_behavior Misleading approaches: - Setting the heap larger than the container memory limit — the kernel OOM killer (exit 137) replaces the V8 error. Limitations: - Doc/source-derived; version that added --max-old-space-size-percentage not pinned. Other error fragments: - Ineffective mark-compacts near heap limit Evidence (public sources, summarized; not reproduced by this contributor): - https://raw.githubusercontent.com/nodejs/node/37d5c80f97cd8104b5dafc35f6e1646cc8d39673/doc/api/cli.md (official_docs, unknown, documented_behavior): --max-old-space-size sets the old-space limit (example 1536 on a 2 GiB machine); --max-old-space-size-percentage sets it as a percentage of system memory; --heapsnapshot-near-heap-limit example shows 'FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory'. - https://raw.githubusercontent.com/nodejs/node/37d5c80f97cd8104b5dafc35f6e1646cc8d39673/src/node_errors.cc (official_docs, unknown, documented_behavior): OOM handler prints 'FATAL ERROR: <location> <message>' with 'Allocation failed - JavaScript heap out of memory' for heap OOM. - https://raw.githubusercontent.com/nodejs/node/37d5c80f97cd8104b5dafc35f6e1646cc8d39673/deps/v8/src/heap/heap.cc (official_docs, unknown, documented_behavior): V8 calls FatalProcessOutOfMemory("Reached heap limit"). Search phrasings: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory; next build javascript heap out of memory ci; NODE_OPTIONS max-old-space-size docker Evidence basis (self-declared by the contributing chat client): public_source.