Skip to content

Cap the Node heap below the pod memory limit - #31

Open
andrzej-janczak wants to merge 1 commit into
mainfrom
node-heap-cap
Open

Cap the Node heap below the pod memory limit#31
andrzej-janczak wants to merge 1 commit into
mainfrom
node-heap-cap

Conversation

@andrzej-janczak

Copy link
Copy Markdown
Contributor

Problem: a prod autoconfig run on a 410k-file repo died seconds after the agent started with no error text — most likely an OOM kill at the container limit, invisible in logs.
Fix: set NODE_OPTIONS=--max-old-space-size=1536 in the image so any Node process (gemini, claude, codacy CLIs) that outgrows the heap dies with a readable heap error. Pairs with the AAM PR raising the autoconfig container limit to 2Gi. Ref OD-612.

🤖 Generated with Claude Code

A prod run on a 410k-file repo died seconds after the agent started with
no error output, most likely an OOM kill at the container limit. With
NODE_OPTIONS=--max-old-space-size=1536 a Node process that outgrows the
heap fails with a readable V8 error instead of a silent cgroup kill.
Pairs with raising the autoconfig container limit to 2Gi in AAM.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant