Issue metadata
Sign in to add a comment
|
Very high CPU usage on renderer |
||||||||||||||||||||||||
Issue descriptionhttps://listnr.corp.google.com/product/208/report/82514976872 very high CPU usage on certain pages. https://www.windsor-hotels.co.jp/en/ uses more than 100% on samus This google search result uses more than 50% pages when visible. https://www.google.com/search?q=windsor+hotel+toya&rlz=1CAZZAD_enUS768US768&oq=windsor+hotel+toya&aqs=chrome..69i57j69i60l3.141j0j1&sourceid=chrome&ie=UTF-8 Submitted on: November 05, 2017 21:28 (PST) Product Version: 62.0.3202.74 beta Country: US Language: en Label: #label>Dogfooders, #label>Managed, #label>Samus, #label>BetaChannel, #label>Hotrod>GCommUser Experiment ids: keyboard_arrow_down Browser Info keyboard_arrow_down Product Specific Data keyboard_arrow_up CHROME VERSION 62.0.3202.74 beta CHROMEOS_AUSERVER <URL: 1> CHROMEOS_RELEASE_BOARD samus-signed-mp-v3keys CHROMEOS_RELEASE_DESCRIPTION 9901.54.0 (Official Build) beta-channel samus CHROMEOS_RELEASE_TRACK beta-channel CHROMEOS_RELEASE_VERSION 9901.54.0 ENTERPRISE_ENROLLED Managed expi 3300109 3300133 3312621 3313322 hardware_class SAMUS E25-H7R-W5L routes default via <IPv4: 1> dev wlan0 metric 1 <IPv4: 23>/30 dev br0 proto kernel scope link src <IPv4: 18> <IPv4: 52>/24 dev wlan0 proto kernel scope link src <IPv4: 1>42 [REDACTED_PSD] web_data count: 74 Product Specific Binary Data keyboard_arrow_up
,
Nov 7 2017
How does this compare to the same pages on Linux? Seems unlikely this is Chrome OS specific.
,
Nov 8 2017
(Corrected MS to 62) I just got an update today (63.0.3239.26 beta) and this no longer repros.
,
Nov 9 2017
Looks like a temporary bug that is already fixed?
,
Nov 9 2017
I don't know if this is fixed on 62 stable.
,
Nov 10 2017
We def need to confirm the status on stable.
,
Nov 14 2017
I'm looking at R62 performance regressions on R62 affecting Samus and Paine.
,
Nov 15 2017
thanks bccheng@!
,
Nov 15 2017
,
Dec 9 2017
Recently there was a performance issue confirmed in R62 that is caused by failing to set the min_filelist_kbytes large enough to accommodate the footprint of ARC++ and Chrome .text sections. That has been fixed recently and the fix has been merged to R63+. Let's dup the bug for now and re-open it if it happens in later releases. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by osh...@chromium.org
, Nov 6 2017