20.05.2025, 09:49
I've got LM reboot after almost 12months uptime. My logs shows that CPU usage was steadily increasing during 24h until it peaked at 100% and caused reboot.
When looking further, i found that system have memory consumption higher than usual, and pinned it down to lmcloud process (24hrs after reboot it already consumes 24mb memory).
In the cloud logs I found that server connection was constantly dropping for some time (i'll address that on network level, but that's a different topic), so my theory is that lmcloud daemon have resource leak on disconnect. My ask to developers is to check if this is true assumption and try and fix the leak as it causes system instability over time.
When looking further, i found that system have memory consumption higher than usual, and pinned it down to lmcloud process (24hrs after reboot it already consumes 24mb memory).
In the cloud logs I found that server connection was constantly dropping for some time (i'll address that on network level, but that's a different topic), so my theory is that lmcloud daemon have resource leak on disconnect. My ask to developers is to check if this is true assumption and try and fix the leak as it causes system instability over time.
