I found this problem frequently in the web in combination with raspberry pi, but no general solution. I'm running node-red in a docker container on ubuntu. I installed this two weeks ago, so all versions should be up to date. Im running quite "heavy" workflows with hundreds of variables and message…

If in doubt always suspect the chart :slight_smile:

Did some overall heap profiling and the table node seems to be most expensive element (I removed the ui_led cos I didn't want to install it to this machine) Feeding new data every second to table node sounds for me a little bit not very optimized way to have tables on dashboard. Is it? So what if …

I plan to visualize some process data, that are updated at least once a second. So a table seems to be a good structuring element for displaying the data. The same is for the chart, since in pocess visualization charts are quite important. My question is possibly, if I utilize the dashboard nodes i…

For table node it is not a bug but design decision. It is not targeted to rapid changes. Mostly tables have pretty steady content cos who can read many fast changing numbers (or what ever in it) and make some resolution on that info. It is not task for human.

Hmmm ... you migth be right, but if the table is the reason and if I update the table e.g.once a minute, the leakage will finally kill the browser 60 times later than now. I have running a dashboard on it's own for a few days now, so I think the dashboard is not the origin of the problem. I also re…

I still run your setup without table node and I can't see any growing. Runs pretty steady last 40+ minutes. [image] mhechthz: I also read in the web, that the gauge nodes are critical After hour of running still steady. I think you can go on with gauges safely. (Happy to have ui_level includ…

[image] mhechthz: that it is common to display also fast changing data for human This is most probably because of bad planning, luck of resources and time and painful legacy to support and no way to have long enough down time to change something. Yes I have seen such.

Which version of node-red you are running? And on which os? I use ubuntu 18.x with docker and the node-red inside docker is 1.0.4. In meanwhile I have again more than 1 GB starting from below 300 kB. Edit: I now removed the ui_led, since this is the main difference ?!?

[image] mhechthz: if I update the table e.g.once a minute, the leakage will finally kill the browser 60 times later than now. If it does then that would indicate a bug.

15 Apr 08:09:53 - [info] Node-RED version: v1.0.5 15 Apr 08:09:53 - [info] Node.js version: v12.13.0 15 Apr 08:09:53 - [info] Windows_NT 10.0.18362 x64 LE 15 Apr 08:10:07 - [info] Loading palette nodes 15 Apr 08:11:01 - [info] Worldmap version 2.1.2 15 Apr 08:11:03 - [info] Dashboard version 2.19.4…

Node-RED

Node-RED Forum

Memory leakage with simple dashboard

Dashboard

system Closed 17 May 2020 15:20 18

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

Topic		Replies	Views
Dashboard become unresponsive Dashboard	13	1354	7 July 2020
Slow dashboard performance across machines General node-red-dashboard	9	398	31 July 2023
Dashboard ui crashing Dashboard	11	1339	16 December 2018
Dashboard crashing on different browsers Dashboard	23	1604	16 October 2020
Node Red memory consumption / "leak" affecting android tablets General node-red-dashboard , flexdash	14	540	20 October 2023

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Memory leakage with simple dashboard

Related topics