> phone almost burns my hand> check running processes> you again!> *reboots*
-
> phone almost burns my hand
> check running processes
> you again!
> *reboots* -
> phone almost burns my hand
> check running processes
> you again!
> *reboots*@allpurposemat Oh. Wow. I heard there was a usage issue, but I didn't know it was *that* bad.
-
> phone almost burns my hand
> check running processes
> you again!
> *reboots*@allpurposemat@mastodon.gamedev.place I wonder why this happens?
I am just guessing, but the first thing that comes to mind is that a lot of Gnome is scripted in Python, which is a language that tends to have trouble with performance. But it's hard to say without doing some real performance profiling.
-
@allpurposemat Oh. Wow. I heard there was a usage issue, but I didn't know it was *that* bad.
@justsoup normally it's fine, but once or twice a day it gets in a state where gnome-shell uses 100% of a CPU core. It does not let go until the process is restarted (relog or reboot). It'd be nice if it auto-rebooted when it happens honestly, the biggest thing with this is the battery life drain.
-
@allpurposemat@mastodon.gamedev.place I wonder why this happens?
I am just guessing, but the first thing that comes to mind is that a lot of Gnome is scripted in Python, which is a language that tends to have trouble with performance. But it's hard to say without doing some real performance profiling.
@ramin_hal9001 Thanks for the suggestion. I am *really* trying to stick with gnome mobile for now but if/once I am finally broken then Phosh is the next UI I will try :)
I did do profiling, and when the bug happens >90% of my sampling was in the JS runtime. I reported my findings here: https://gitlab.gnome.org/verdre/gnome-shell-mobile/-/issues/70
Sadly no solution in sight yet, but would love to have more eyes look at this!
-
undefined aeva@mastodon.gamedev.place shared this topic
-
> phone almost burns my hand
> check running processes
> you again!
> *reboots* -
@ollieparanoid Thanks, I did try this at FOSDEM but the CPU usage came back sadly. I'll give it a shot next time it happens :)
@pavel by any chance were you experiencing something similar to me, or was the gsd-color process itself the one maxxing out a core?
-
undefined oblomov@sociale.network shared this topic