New Google ChromeOS updates cause 100% CPU usage, heating issues

Re:New Google ChromeOS updates cause 100% CPU usage, heating... by tyingq on Sunday September 27, 2020 @06:00PM (#24610471)

From the bug report[1] "E KernelUidCpuFreqTimeReader: Failed to read /proc/uid_time_in_state: java.io.FileNotFoundException:"

So, sort of because of missing files, but more about ignoring an exception and running on into code that's probably looping.

[1] https://bugs.chromium.org/p/chromium/issues/detail?id=113245...

[ Parent | on HN ]

Re:New Google ChromeOS updates cause 100% CPU usage, heating... by jeffbee on Sunday September 27, 2020 @07:17PM (#24611029)

It seems the class in question exists in Android 8 and not but not 10 or 11.

https://android.googlesource.com/platform/frameworks/base/+/...

[ Parent | on HN ]

Re:New Google ChromeOS updates cause 100% CPU usage, heating... by innagadadavida on Sunday September 27, 2020 @10:19PM (#24612306)

Should this type of problem be caught reliably during QA or were there any rare conditions that triggered it?

[ Parent | on HN ]

Re:New Google ChromeOS updates cause 100% CPU usage, heating... by tibbydudeza on Sunday September 27, 2020 @06:21PM (#24610627)

Odd as I don't find such a proc interface in my Ubuntu WSL. It seems to be Android specific.

[ Parent | on HN ]

Re:New Google ChromeOS updates cause 100% CPU usage, heating... by cesarb on Sunday September 27, 2020 @07:32PM (#24611130)

I see no reference to that file in a checkout of the upstream Linux kernel I had here, and I never saw that file in /proc in any Linux system I've played with, but looking at my phone (with Termux) I do see that file. I agree, it seems to be Android specific.

[ Parent | on HN ]

Re:New Google ChromeOS updates cause 100% CPU usage, heating... by tyingq on Sunday September 27, 2020 @07:46PM (#24611222)

It's filed as a ChromeOS bug...Chromebooks and family.

[ Parent | on HN ]

Re:New Google ChromeOS updates cause 100% CPU usage, heating... by snazz on Sunday September 27, 2020 @08:20PM (#24611506)

So if it doesn't exist in regular Linux or ChromeOS, then it must be an Android feature that was accidentally enabled in non-Android builds.

[ Parent | on HN ]