Browser - Bad render performance

General
1

Hello.
I am using following environment:

  • Microsoft Server 2025 (Running on VM)
  • Microsoft Edge Browser (Version 153.0.4234.48)
  • NodeJS 24.21.0 LTS (latest)
  • Node-RED 5.0.7 (latest)
  • Reverse Proxy IIS
  • Microsoft Defender

I am working via RDP on the server. Until a few weeks a ago there was no problem.

Current Problem:
If I open a Node-RED project with flows which contains more nodes (in particular with link nodes) then the performance in the browser is very poor. If you click between the flows the browser jumps to NOT RESPONDING. It also occurs if you switch from the browser window to a another app and back to the browser window.

I checked with the DevOps Tools but I can't see any problems.
I tested with and without the reverse proxy.
I removed all separate installed nodes.
I removed all own implemented nodes.
I started with a fresh settings.js and with a fresh .node-red directory
I tested with the Google Chrome browser.
=> The problem still exists if you create a flow with some nodes, link-nodes.

I also tested with Firefox -> There is no problem. All works smoothly.

It seems there is a problem in combination of Node-RED and the current rendering-engine of chromium based browsers.

Does anyone has the same problem and how could this fixed.

Thanks and have a nice week.
Markus

2

There is certainly not a general problem using chrome browsers with node-red so it must be something specific to your use case. Possibly an issue with RDP and the chrome browsers. AI suggests disabling hardware acceleration in the browser.

3

OK I will check the combination of MS Edge and RDP.
Hardware-Acceleration is also disabled but nothing changed.

4

I have a tip:
Browser performance is terrible when Dashboard 2.0 is open in the right sidebar. If you close it or select “Debug,” for example, the performance issue goes away.
I've already reported this as an issue, but so far without success.

Result: It worked for me.
Best regards,
Hubertus

5

Thanks.
But I have a blank node-red instance without any installed packages and the error occurs.
In my eyes there must be anything in the chromium engine, settings in the Edge browser or so.

Best regards, Markus

6

Update - New information:
It must be something on the server-side.
If I use the MS Edge (Version 151.0.4129.107) browser of my client (also VM but Windows 11) then it works fine.

I will close this post because it is not a Node-RED error.
Thanks for your ideas.