I've built a node red dash to monitor a sensor array. This dash is displayed persistently, but some frustrating memory leak issues cause it to crash periodically as the browser consumes all available memory. A simply refresh fixes the issue so, as a workaround, I was hoping there would be a way to automate an hourly browser refresh in node-red. I assume I might be able to do this with the ui_control node but I'm just not sure how to go about it.
If anyone has any tips for tracking down memory leaks, I'm all ears on that front as well!
This is in an industrial application so we are displaying a lot of data. Line charts are plotting 10min intervals for 24hrs so roughly 150 points of data. Several of these per tab with 6 tabs and growing now. I've also set up aggregator nodes to look at min/max/avg daily, so I assume those are storing a lot of data as well.
I'm not sure that this is the issue though. When I look at the chrome task manager I can see the memory useage creep up in real time despite all the line graphs and aggregator nodes being fully populated. If I'm looking at the last 24hrs on a line chart, for each point I add, I'm discarding an old one, no? If that's true my layman brain wouldn't expect accumulating memory useage.
I don't know exactly, but I seems to be once every 6 hours or so. I have a somewhat flaky chrome extension doing an hourly fresh now and as long as the extension works and executes the refresh, all is well.
Also, IDK if this could be related, but I am using a ui-control node to change tabs every 30s. This dash is a hands-free way to monitor machine health in real time so I want it to page through the data frequently. Any reason this behavior would accrue memory useage?
