High CPU Web Browser Tab Crash

Questions
,
1

Hello.

I am using latest version 1.41.0

I have 2 very simple workflows that when chained the whole browser tab is stuck and crashes. I check the cpu via profiling and it is excessive.

You can replicate it by following these steps.

First create the first workflow:

Then create the second workflow:

From the second workflow add to the Execute Workflow Node, Workflow ID the ID of the first workflow.

Run the second workflow, wait to finish and try to double click the Increment Counter node.

The whole browser tab will stuck. Tried with Firefox and Edge browsers. Same thing happend.

2

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:
3

Hey @Mulen,

In theory what you are doing shouldn’t be possible as you setting the value of a previous node which we should be blocking.

You are also using very old syntax in your expressions which could be causing issues as well but to be honest if you are trying to make a counter you can make the workflow a lot simpler by just using {{ $runIndex }} which will increase by 1 each time the node runs so your workflow then just becomes…

I will still get a ticket created for this as some point though as even though it shouldn’t work in the way you are using it we still shouldn’t crash the UI like that.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.