Slashdot is powered by your submissions, so send in your scoop

 



Forgot your password?
typodupeerror
×
Google Bug

Google Patches ChromeOS Update Bug That Caused 100% CPU Usage (techradar.com) 7

"Hello Chrome OS Community," posted one of Google's community managers Wednesday. "Thank you for raising this issue, and for your patience as we work to resolve this. Our team has identified the issue and is rolling out a fix to affected devices."

The issue? ChromeOS users reported the latest updates "cause a Google Play Store service to utilize 100 percent of their CPUs..." according to TechRadar, "making their devices hot and leading to performance issues." As reported by BleepingComputer, after upgrading their devices to ChromeOS version 85.0.4183.108 and later users have faced a number of issues including apps that are running erratically, devices getting hot, fans running at high speed and batteries draining much too quickly. Upon investigating these issues further, users discovered that they were caused by the Google Play 'com.android.vending:download_service' utilizing 95 to 100 percent of their devices CPU for an extended period. This service is used to download new updates from the Google Play Store when they become available. However, a bug in the service causes the CPU to run at 100 percent power all of the time even when a new update is not available.
Bleeping Computer reported last Sunday that the issues didn't affect all Chromebooks, but was reported by users of Acer Chromebooks, ASUS Chromebook Flip, and Galaxy Chromebooks. "One user stated they resolved this issue by rolling back to an older Google Play Store version."
This discussion has been archived. No new comments can be posted.

Google Patches ChromeOS Update Bug That Caused 100% CPU Usage

Comments Filter:
  • About time! Starting to sweat in here with all the heat...

  • by Freischutz ( 4776131 ) on Sunday October 04, 2020 @10:44AM (#60571006)
    Good, now fix the legion of bugs that eat up 100% of memory given enough time.
    • "Good, now fix the legion of bugs that eat up 100% of memory given enough time."

      The old browsers Firefox 56.0.3 and Waterfox 56.2.8 allow the use of the old, excellent add-ons, but use a lot of CPU and add memory use when you have a lot of windows and tabs open, and aren't looking at them. Why? Who wants the CPU and memory time?

      The latest version of Pale Moon [palemoon.org] doesn't do that. Pale Moon gets frequent updates [palemoon.org]. Pale Moon uses all the old add-ons, except that it won't allow the Ghostery add-on, but requir
  • Never, ever, ever patch software the moment an update comes out. Turn off automatic updating in all software. Sit back and wait for others to take the plunge so you can find out about shitfests like this one.

    Also, as this comes on the heels of Microsoft's patch fiasco [slashdot.org], it is quite obvious software companies aren't bothering to follow simple procedures to weed out these bugs and instead are using the end user as guinea pigs. Demand payment for being a quality tester.

  • I didn't know Chomebooks had a CPU. I thought it was just an Ethernet card with a keyboard and display. Obviously Google isn't really good at this cloud thing.

Top Ten Things Overheard At The ANSI C Draft Committee Meetings: (5) All right, who's the wiseguy who stuck this trigraph stuff in here?

Working...