N8n_runners_max_old_space_size

Questions
1

Why release if known issue the old space size fix doesnt work. or add a switch to disable this feature – { “errorMessage”: “Node execution failed”, “errorDescription”: “This can happen for various reasons. Please try executing the node again. If the problem persists, you can try the following:

1. Reduce the number of items processed at a time, by batching them using a loop node
2. Increase the memory available to the task runner with ‘N8N_RUNNERS_MAX_OLD_SPACE_SIZE’ environment variable”, “errorDetails”: {}, “n8nDetails”: { “n8nVersion”: “2.0.3 (Self Hosted)”, “binaryDataMode”: “filesystem”, “stackTrace”: [ “Error: Node execution failed”, " at DefaultTaskRunnerDisconnectAnalyzer.toDisconnectError (/usr/local/lib/node_modules/n8n/src/task-runners/default-task-runner-disconnect-analyzer.ts:32:10)“, " at TaskBrokerWsServer.removeConnection (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker-ws-server.ts:164:58)”, " at WebSocket. (/usr/local/lib/node_modules/n8n/src/task-runners/task-broker/task-broker-ws-server.ts:148:15)“, " at Object.onceWrapper (node:events:634:26)”, " at WebSocket.emit (node:events:531:35)“, " at WebSocket.emitClose (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/ws/lib/websocket.js:265:10)”, " at Socket.socketOnClose (/usr/local/lib/node_modules/n8n/node_modules/.pnpm/[email protected][email protected][email protected]/node_modules/ws/lib/websocket.js:1291:15)“, " at Socket.emit (node:events:519:28)”, " at TCP. (node:net:346:12)" ] } }Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
2

Hey,

The task runner is running out of memory. Try this:

If using Docker, add this to your environment:

N8N_RUNNERS_MAX_OLD_SPACE_SIZE=4096

If running via npm:

bash

export N8N_RUNNERS_MAX_OLD_SPACE_SIZE=4096

Start with 4096 (4GB). If it still fails, bump it up to 8192.

Also, how many items are you processing? You might need to batch them using a loop node to handle smaller chunks at a time.

What’s your setup - Docker or npm? And how many items typically go through your workflow?

3

This instance I run in coolify I tried added to environment variable no luck i was able to roll back. what purposes does this feature serve is my real question