MaxListenersExceededWarning ONLY when "setting" a field for pagination

[unicornParty]

{{$(‘offset’).item.json.offset ++ }}
N8N freezes when I type the second “+”
This HTTP Request is returning 2 items, yet it triggers the crash.

• Chrome freezes: “the page is unresponsive.”
• N8N execution history doesn’t indicate errors

**#DATABASE LOG:**
2024-10-14T23:48:10.416909925Z 2024-10-14 23:48:10.416 UTC [21] LOG: checkpoint complete: wrote 376 buffers (2.3%); 0 WAL file(s) added, 0 removed, 0 recycled; write=37.536 s, sync=0.003 s, total=37.545 s; sync files=21, longest=0.002 s, average=0.001 s; distance=2761 kB, estimate=2761 kB

**#N8N LOG**
2024-10-14T23:43:16.815803080Z - Walmart Get Items (ID: Pj4sNwo250mTMFCS)
2024-10-14T23:43:16.856825640Z [Recovery] Logs available, amended execution
2024-10-14T23:43:17.554808163Z [Recovery] Logs available, amended execution
2024-10-14T23:43:17.671136370Z [Recovery] Logs available, amended execution
2024-10-14T23:43:17.780962758Z [Recovery] Logs available, amended execution
2024-10-14T23:43:17.833504638Z [Recovery] Logs available, amended execution
2024-10-14T23:43:17.876484303Z [Recovery] Logs available, amended execution
2024-10-14T23:43:17.927286920Z [Recovery] Logs available, amended execution
2024-10-14T23:43:17.969117517Z [Recovery] Logs available, amended execution
2024-10-14T23:43:18.242389233Z [Recovery] Logs available, amended execution
2024-10-14T23:43:18.465723178Z [Recovery] Logs available, amended execution
2024-10-14T23:43:18.516642554Z [Recovery] Logs available, amended execution
2024-10-14T23:43:18.549171168Z (node:7) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 editorUiConnected listeners added to [Push]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
2024-10-14T23:43:18.549233367Z (Use `node --trace-warnings ...` to show where the warning was created)
2024-10-14T23:43:18.601188206Z [Recovery] Logs available, amended execution
2024-10-14T23:43:18.689635389Z [Recovery] Logs available, amended execution
2024-10-14T23:43:18.776748657Z [Recovery] Logs available, amended execution
2024-10-14T23:43:18.817441806Z Version: 1.62.5

Information on your n8n setup

• n8n version: - 1.62.5
• Database: - Postgres
• Running n8n via: Caprover → Docker?
• Operating system: VPS?

[n8n]

It looks like your topic is missing some important information. Could you provide the following if applicable.

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

[Jon]

Hey @unicornParty,

That sounds interesting, I suspect as we run the javascript in the browser when you use an expression to validate it we might be constantly checking it and increasing it.

I have just managed to reproduce it and I have created NODE-1874 as the dev ticket to resolve this, For now though it looks like using {{$('offset').item.json.offset +1 }} works

[unicornParty]

@Jon

{{$('offset').item.json.offset +1 }}

The +1 doesn’t paginate so it was returning the same rows.

I just tried this on another VPS and the same thing occured.