> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/hosting/scaling/memory-errors.md).

# Fix memory issues on self-hosted Duaer

Memory-related errors when self-hosting Duaer: how to identify and avoid them.
## Identify and respond

The error text is still JavaScript heap out of memory. How a workflow carries less data is covered under [flow memory errors](/flow-logic/error-handling/memory-errors.md). This page covers process heap size and whether queue mode moved executions to other processes.

A larger Node.js heap helps with occasional peaks. It does not stop every execution from growing. Do not use the removed in-memory binary mode — refer to [binary data](/hosting/scaling/binary-data.md). Each worker has its own heap and does not borrow free memory from another.

You can raise the V8 old-space limit with `NODE_OPTIONS=--max-old-space-size=SIZE`.
## Questions

### Are the hosting and flow memory pages different failures in Duaer?

Same failure: a full heap. The flow page covers carrying less data; this page covers process heap and workers. Change both sides.

