Ok pushed v3.13.39 now
Thanks. Installed and running. I will watch it
1 Like
Ok, sorry for the trouble. Hope we can crack this.
1 Like
sorry, new crash, e52a7328-0d9c-40d6-90a7-f53678863eab
this time auto restart
It is hard as nothing that points to the problem you face.
stderr:
⚠ The app has crashed.
CPU Warning Limit Reached
Ah, oké. Hmm, I will look for more apps with cpu usage, or, is the limit per app you know?
Yesterday my Homey pro crashed, a restart fixed that.
I will push another with more verbose logging.
I know so it is something specific that you face as this is what I have and spikes are the ones when I test/stop/start the app which is expected.
That’s how it should be, you’re right. Weird, over time the cpu usage goes up
Could it be another app (Slim laden) that has an impact on your app (same battery environment, P1 etc)?
Last 6 hours
It is your environment not mine. 
But I don’t know what that app does, no code in github to see so cant give a proper answer to it.
If that is hammering your P1 and Battery with fetches every second ish it starts to cripple everything around.
Maybe as a test temporary stop that app and see what happens?
Other app is closed, there after again a crash, cpu usage goes between 20 and 10. Auto restart.
03e249bf-4ac1-4e8b-ac97-987b3135881a
Ok sent me a few reports (before you think it crashes). I recon we miss info due to the crash somehow.
89ce5104-5485-495e-8311-08727224ca28 running now again
41a2cf7a-2483-43df-940b-97cf2a3a5178
99431e5d-f641-48d6-8033-8faec769116d
Ok another test version .41 now.
Running and waiting
.42 nu. I think your 9? sockets CPU spike at every restart/crash. I added an extra delay there upon init to spread them.
1 Like
