Informational notification.
This post is a trending issue.
Feb 10, 2020
High CPU load on web when not minimized
Hi, posting from my GV account, and this issue happens on multiple accounts/users, but mine is 8332.
When viewing https://voice.google.com from the browser (tested in Firefox, Chrome, and Chromium) and highlighting a conversation, leaving the window open results in ~40% CPU usage constantly. If I minimize the window, the CPU utilization goes away.
I can observe this behavior in multiple operating systems, including Ubuntu 18.04 as well as Windows.
From monitoring the debug console, this appears to be a refresh command running in the UI thread. I couldn't debug very much because of the minified JS, but running a JS processor on it shows the underlying cause. I'm sure it could be easily determined with unminified code.
I am surprised to not see any posts related to this, as I've observed it across every account/user/friend I've checked with.
Thanks!
Informational notification.
This question is locked and replying has been disabled.
Community content may not be verified or up-to-date. Learn more.
All Replies (8)
Feb 24, 2020
Also, when I close the Voice tab, the voice.google.com/u/0/service-worker.js process remains running.
And, Voice seems to startup and run in the same Process ID as other resource-intensive processes, and rarely by itself in its own Process ID.
Last edited Feb 24, 2020
Hi folks:
For the technically-inclined, would you please help me collect some data for Google Voice engineering?
Use the same computer(s) that is/are experiencing the behavior, and use Chrome Browser. Go to this page: chrome://serviceworker-internals/
Look for this:
Let me know if the service worker's running status is "running" or "stopped". Thanks.
Last edited Mar 3, 2020
Mar 3, 2020
Mar 3, 2020
Here's what you asked for and a bit more:
Scope: https://voice.google.com/u/0/
Registration ID: 1367
Navigation preload enabled: false
Navigation preload header length: 4
Active worker:
Installation Status: ACTIVATED
Running Status: RUNNING
Fetch handler existence: DOES_NOT_EXIST
Script: https://voice.google.com/u/0/service-worker.js
Version ID: 22388
Thanks very much. After we get a few more samples, we'll have something meaningful for Google Voice to investigate.
Adam, would you please try this: go back to the serviceworkers page, and try to unregister that serviceworker, then close and reopen your browser, try recreating your high CPU usage, and report back here what happens? Thanks!
Mar 23, 2020
Hi, just wanted to add to this. I've noticed the high cpu usage only happens when a Message conversation with a long history is in focus. This only happens to one cpu core. If I click onto a conversation with only a few messages, the cpu core usage drops. If I select the conversation with a long history, including pictures, then the cpu core usage skyrockets again. This is only happening with one of my message conversations, the longest one. I don't have any conversations of comparable length to attempt to recreate the issue with.
@Bluescat - Following your above instructions, here is a screenshot before unregistering:
After unregistering and closing/reopening the browser, I am able to recreate the issue. Clicking on the conversation with a long message history and many messages spikes the CPU core.
Happy to help test any way I can. I've got a lot of time on my hands right now, as we all do.
Computer info:
AMD TR 2920x
ASROCK x399 Phantom
Samsung 970 EVO 1TB
64GB G.SKILL DDR4-3200
EVGA 2080 Ti FTW3
Windows 10 Version 1909 (OS Build 18363.720)
Chrome Version 80.0.3987.149 (Official Build) (64-bit)
Thanks for helping us with this, Bluescat.