Skip to content

Larkhost Community

Menu

Community

Topics Categories Tags Members Leaderboard Badges About

Categories

General Fresh Produce Questions / Help Show & Tell Django Rails Laravel Node Python Back Porch

Tags

burrows pods deploys networking processes proxy agents auth autoscaling autostop

Loading…

Forum
Node

Node.js app memory climbs until OOM — only on Larkhost

bramblefox · 2 replies · 165 viewsjavascript memory

bramblefoxRegularyesterday

bramblefoxAuthorRegularyesterday

Related topics

Rails 8 solid_queue on Larkhost: one pod or two?1 reply
Pod stuck in "starting" for 15 hours after resume1 reply
Pod restarts by itself 1–3 minutes after waking from idle1 reply
How is burrow RAM billed? Does it include the page cache?1 reply
Show & Tell: a tiny job runner on pods that sleep between jobs2 replies
The back porch: what are you running on a single shared-cpu pod?3 replies

Suggested topics

Larkhost support: community vs. email, 2026 edition (read this first)0 replies
The back porch: what are you running on a single shared-cpu pod?

3 replies

Python 3.13 images are now the default for new launches2 replies

Laravel queues stop processing after a deploy1 reply

Rails 8 solid_queue on Larkhost: one pod or two?1 reply

Locally, memory is flat at ~180 MB. On a 512 MB pod it climbs to the limit over six hours and the pod is killed.

Node sizes its heap from the machine, not the container, on some versions. Set NODE_OPTIONS=--max-old-space-size=384 and see if it levels out.

Flat at 240 MB after a day. That was it.