Node-Red Dashboard / Raspberry Pi / Charts and Memory

Greetings!

  • I have the node red dashboard running on a raspberrypi 3b with a 7" touchscreen
  • Mir-kiosk with wpe-webkit and the node-red-rpi snap by @ogra
  • unbuntu core 18

Everything is great until I let it run for a day. For some reason the display began show a strange decaying of the graphics on the dashboard after running for 24hrs or so (see attached image).

13%20PM

I’m assuming this must be a memory issue. I would like to try and impose some garbage collection. Any ideas where I start with that?

Thanks!

I believe the several hundred lines in a row like this in the logs verify my suspicions.

Jun 24 19:08:39 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 338993152/339124224/131072, res+swap = 422076416/422207488/131072
Jun 24 19:09:09 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 339288064/339398656/110592, res+swap = 422371328/422481920/110592
Jun 24 19:09:39 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 339431424/339677184/245760, res+swap = 422514688/422760448/245760
Jun 24 19:10:09 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 339914752/340054016/139264, res+swap = 422998016/423137280/139264
Jun 24 19:10:39 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 341123072/341143552/20480, res+swap = 424206336/424226816/20480
Jun 24 19:11:09 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 345059328/345309184/249856, res+swap = 428142592/428392448/249856
Jun 24 19:11:39 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 342491136/342601728/110592, res+swap = 425574400/425684992/110592
Jun 24 19:12:09 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 343031808/343166976/135168, res+swap = 426115072/426250240/135168
Jun 24 19:12:39 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 340381696/340516864/135168, res+swap = 423464960/423600128/135168
Jun 24 19:13:09 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 340832256/340963328/131072, res+swap = 423915520/424046592/131072
Jun 24 19:13:39 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 341999616/342011904/12288, res+swap = 425082880/425095168/12288
Jun 24 19:14:09 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 344907776/344907776/0, res+swap = 427991040/427991040/0
Jun 24 19:14:39 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 351313920/351371264/57344, res+swap = 431763456/431820800/57344
Jun 24 19:15:09 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 345010176/345194496/184320, res+swap = 425459712/425644032/184320
Jun 24 19:15:39 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 345247744/345341952/94208, res+swap = 425697280/425791488/94208
Jun 24 19:16:09 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 344641536/344809472/167936, res+swap = 425091072/425259008/167936
Jun 24 19:16:39 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 341344256/341504000/159744, res+swap = 421793792/421953536/159744
Jun 24 19:17:09 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 341295104/341303296/8192, res+swap = 421744640/421752832/8192
Jun 24 19:17:39 localhost wpe-webkit-mir-kiosk.browser[1231]: Memory pressure relief: Total: res = 341413888/341549056/135168, res+swap = 421863424/421998592/135168

This is interesting, since i started with the node-red-rpi snap i have a similar setup running here (3b+ 7" screen (not touch and via config.txt set to 1080p)) and do not see such issues … i’m wondering if some javascript of your dashboard goes wild here … (my setup does pretty much just use the default gauges and graphs with no modificatons)

you should probably start with:

though this will indeed most likely just postpone the issue a bit.