{"id":"69c71bc86ebd8da69ae50a68","title":"2026 03 17","path":"how-to/committee/release-notes/2026-03-17","contentMarkdown":"# 17-Mar-2026 — reduce worker Node heap to 128 MB for Serenity subprocess [#189](https://github.com/nbarrett/ngx-ramblers/issues/189)\n\n## [build 567](https://github.com/nbarrett/ngx-ramblers/actions/runs/23672501568) — [commit 54434f1](https://github.com/nbarrett/ngx-ramblers/commit/54434f10e4350ac4da7538b52e0f5be478223f93)\n\n_____\n\n### **walks-export**: reduce worker Node heap to 128 MB for Serenity subprocess ([#189](https://github.com/nbarrett/ngx-ramblers/issues/189), [#114](https://github.com/nbarrett/ngx-ramblers/issues/114))\n\nThe Serenity worker subprocess was inheriting the parent server's\n460 MB Node heap limit, which is excessive for a process that only\norchestrates Chrome via WebdriverIO. This left less headroom for\nChrome itself within the VM's memory budget.\nSet NODE_OPTIONS=--max_old_space_size=128 explicitly on the spawned\nprocess, freeing ~330 MB for the Chrome session. Stopgap until #114\nmoves the worker to a dedicated process.","contentHtml":"

17-Mar-2026 — reduce worker Node heap to 128 MB for Serenity subprocess #189

\n

build 567 — commit 54434f1

\n
\n

walks-export: reduce worker Node heap to 128 MB for Serenity subprocess (#189, #114)

\n

The Serenity worker subprocess was inheriting the parent server's\n460 MB Node heap limit, which is excessive for a process that only\norchestrates Chrome via WebdriverIO. This left less headroom for\nChrome itself within the VM's memory budget.\nSet NODE_OPTIONS=--max_old_space_size=128 explicitly on the spawned\nprocess, freeing ~330 MB for the Chrome session. Stopgap until #114\nmoves the worker to a dedicated process.

\n"}