Could you share a very simple repro flow that you can observe the same thing happening? This way someone here can take a look. Thanks
@AllanOricil
What are you referring to exactly?
Anyway, after having sorted out the errors I had, it's evident that the issue was not NodeRed related but to the lxpanel process. I tried to restart that process and the memory usage went immediately down to 15%. Looking around I found a thread were it seems that lxpanel is poorly written and some of its widgets have memory leaks.
I am trying disabling the widgets one by one and see what happens.
