Google Releases Fix For ChromeOS Bug Causing 100% CPU Utilization

Google has released a temporary fix for a ChromeOS bug that causes 100% CPU utilization in Chromebooks.

Last week, BleepingComputer broke the story that the ChromeOS 85.0.4183.108 update caused Google Play’s ‘com.android.vending:download_service’ service to utilize 100% of the CPU.

According to Google, the bug is caused by a missing file being unable to report UID proc times.

“After review, users are experiencing this behavior because CrOS is unable to determine delta changes in UID proc times due to missing files,” a Google engineer stated in a now locked bug report.

Since then, a Google employee has posted a workaround for this bug to a Google forum support topic, which resolves the bug by replacing the Google Play Store with the factory default version.

We have also identified steps you can take to apply the fix to your machine as soon as possible:

1. At the bottom right, select the time.
2. Select Settings .
3. Select Apps on the left-hand side
4. Select Google Play Store
5. Select Manage Android Preferences
6. Select Apps & Notifications
7. Select See all [# of Apps] apps OR Apps info
8. Select Google Play Store .
9. Select Disable
10. In the window that appears, select ‘Disable APP.’
    Note: In the window that appears, you’ll see: ‘If you disable this app, Android and other apps may no longer function as intended.” By selecting ‘Disable APP,’ you will temporarily disable the Play Store, and this will be re-enabled once you complete this troubleshooting flow.
11. In the window that appears, select ‘Ok.’
    Note: In the window that appears, you’ll see: ‘Replace this app with the factory version? All data will be removed.’ By selecting ‘Ok,’ you will temporarily replace the Play Store app with the factory version.  Your other apps will not be affected.
12. Remain on the same screen and select ‘Enable’, and then close the window.

Completing all of these steps will resolve this issue.

While the above fix will resolve the high CPU utilization issues, it will ultimately be fixed in an upcoming ChromeOS update.

Google stated that it would continue to post updates to the Google forum support topic for this issue.