# 17-Mar-2026 — reduce worker Node heap to 128 MB for Serenity subprocess [#189](https://github.com/nbarrett/ngx-ramblers/issues/189)

## [build 567](https://github.com/nbarrett/ngx-ramblers/actions/runs/23672501568) — [commit 54434f1](https://github.com/nbarrett/ngx-ramblers/commit/54434f10e4350ac4da7538b52e0f5be478223f93)

_____

### **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))

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