We are struggling with a memory problem. The attached flow should be ready to run but following nodes are needed: node-red-contrib-linux-memory (0.8.1) node-red-contrib-pid (1.1.7) node-red-dashboard (2.28.1) To make it easier for somebody to test we are saving the graph data in the default conte…

Thanks again @Colin ..okay, let me try to answer all the questions: We get these controllers preconfigured from the manufacturer (it's not a Pi, our system has 512 MB RAM). If I look at the service config file, it doesn't seem to have a max_old_space_size set. How or where can I check what size par…

[image] rko: If I look at the service config file, it doesn't seem to have a max_old_space_size set. That is probably why node-red is using up all the memory before garbage collecting. For a system with 512MB you should possibly set it to 256. Then node red will release memory when it gets …

[image] rko: Do I have to destroy the msg manually No, you don't need to destroy anything manually, once it gets to the point that it is no longer referenced anywhere then it will be available for release. The context data exists in a cache in memory even if it is file backed. If, for examp…

Do you really need the locale timestamp there? Could you not use an ISO string instead? My understanding is that the date/time locale handling of JavaScript in general is quite slow and heavyweight. Converting to an ISO string doesn't loose any information and is serialisable. Alternatively, maybe …

Oh wow. @TotallyInformation creating timestamps with toISOString() looks very promising. I let it run for some time and let you know if it's stable. Just need to convert it to local time but that should not be a big deal. And also thank you @Colin for all the valuable information.

As a general rule, it is best to leave timestamps in UTC until you display it. That way you never have to worry about DST and locale issues when calculating and storing things.

Sadly you still do not know the real cause of the problem. It would have been better to try setting the memory limit first in order to check that is the real cause of node-red consuming all the memory. Otherwise if you develop the system further and node-red needs more memory you will hit it again…

We are still testing. I tried to change the memory limit first indeed but it did not have the expected effect. I added the following line to the service file: [Service] Environment="NODE_OPTIONS=--max_old_space_size=256" Since persistent context is somewhere in the memory still (which I did not k…

[image] rko: I tried to change the memory limit first indeed but it did not have the expected effect Does $NODE_OPTIONS appear in the ExecStart line? Did it have any effect? It should have stopped node red from consuming more than 256MB. Which could have crashed node-red if it actually need…

[image] Colin: It should have stopped node red from consuming more than 256MB That's not how max old space works I'm afraid. All it does it provide a hint to the V8 engine to do GC at that level of stack use. It doesn't change the total amount of memory available to Node.js. That in itself w…

Node-RED

Node-RED Forum

Memory problem Dashboard/plotly.js

Dashboard

system Closed 26 March 2021 22:55 27

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

Topic		Replies	Views
Memory leak ?... trouble performance now General	36	2466	13 February 2022
Node Red memory consumption / "leak" affecting android tablets General node-red-dashboard , flexdash	14	540	20 October 2023
Memory leakage with simple dashboard Dashboard	17	954	17 May 2020
Node-Red on RPi restarts after ~2 weeks General	52	915	17 December 2024
Node Red crashed - why? General	12	788	22 March 2022

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 problem Dashboard/plotly.js

Related topics