81 up is when it starts to throttle but can still clock full speed at 81 for a couple of seconds when I was bench testing my Pi4

Link here https://forum.magicmirror.builders/topic/10940/issues-with-mm-freezing-and-rpi3-running-hot/10

@sdetweil I would imagine it’s full around that time mine use to crash every 12 hours without fail, I put it down to ram on the pi3B+ I got the pi 4 4Gb and it doesn’t crash anymore with the help of Watchdog too. Ram just gets eaten on the pi

@sdetweil I believe some one said the swap file was not big enough and the pi was burning through it and when it was full it would crash so I think they upped it to 4Gb

@Detto65 ram over days drop down my 4Gb pi is running 50% free from 87% when it first starts, it’s now 10days thanks to watch Dog and free memory has gone up. I use to get that on the pi 3B it’s a 100% memory that’s used once it gets to that it will crash the pi altogether and you will have to power it down ie reboot. Only way around that was a Cron Job that restarted MagicMirror every 12hours, give that a go, check out how many hours it takes to lock up you may need to make this 6hour intervals

@Detto65 memory install watchdog to help reboot it when it crashes from running out of memory

Not a fork but hue lights https://github.com/michael5r/mmm-hue-lights

@stalker401 i would say it’s running out of memory, as even my Pi4 4Gb does, install watchDog it will restart it when the mirror crashes, electron kills the memory ie takes up too much memory.

@sdetweil updated!

@sdetweil it’s literally just the seconds of the time I’m seeing which I might try to stop not seen any Nest process but I did restart it before this so that error has likely gone, as soon as it happens again I will dev console and check thank you