New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 814658 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Mar 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Delay is seen to open 'Clear browsing data' overlay from chrome://history page

Project Member Reported by mmanchala@chromium.org, Feb 22 2018

Issue description

Chrome Version:  66.0.3350.3/10427.0.0 dev-channel Daisy,Kip and Reks
OS: Chrome

What steps will reproduce the problem?
(1)Sign  into User -> Press 'Ctrl +H' to open chrome://history page -> Now select 'Clear browsing data'  option 
(2)Observe delay is seen to open 'Clear browsing data' overlay
(Please refer Video)

Note:
1.No delay is seen in Linux and WindowsOS 
(Please refer 'Expected_BehaviorInWindowOS' video)
2.Issue is working fine in M-63 and M-64

Expected: No delay should be seen to  open 'Clear browsing data' overlay from chrome://history page
Actual: Instead  So much delay is seen to  open 'Clear browsing data' overlay from chrome://history page

This is Regression Issue as same is working fine in M-65
i.e. not that much delay is seen

@stevenjb : please confirm the Issue
 
Actual_Delay.webm
664 KB View Download
Expected_BehaviorInWindowsOS.mp4
9.2 MB View Download
Expected_NoDelay.webm
455 KB View Download
Cc: dschuyler@chromium.org steve...@chromium.org hcarmona@chromium.org
Labels: -OS-Chrome
Owner: dpa...@chromium.org
Can you please reconfirm that there is a difference between 65 and 66 on the same hardware under the same circumstances (e.g. load both immediately after startup without loading anything else)?

If there is a regression here we should definitely investigate.

This is not likely CrOS specific, just likely more apparant on slower CrOS devices.

Comment 2 by dpa...@chromium.org, Feb 22 2018

Labels: OS-Chrome
Owner: steve...@chromium.org
Based on the following comment
"No delay is seen in Linux and WindowsOS"

adding the CrOS label for now.

> Can you please reconfirm that there is a difference between 65 and 66 on the same hardware under the same circumstances (e.g. load both immediately after startup without loading anything else)?

I tried Linux builds 64 vs 66 on my workstation, visiting chrome://settings/clearBrowserData and measuring the time until the dialog shows up (average of 5 runs):

Linux 64 (stable): 990ms
Linux 66 (Tip of tree): 1096ms

Also tried a Linux ChromeOS build 66 (ToT): 1600ms
Could not find an easy way to run Linux ChromeOS 64/65 locally.

So there seems to be a slow down even in non-CrOS builds, although ChromeOS seems to be more than 50% slower compared to non-CrOS builds.
Cc: abodenha@chromium.org
(Running Linux ChromeOS on a branch should be exactly the same as running a Linux build on a branch, just add target_os = "chromeos" to args.gn.)

I'm not sure what I am expected to do for this? As we know, CrOS Settings is larger, and CrOS devices are much slower, so a small regression on a fast Linux Desktop is very likely to be much exaggerated on a CrOS device.

Perhaps we need to revisit ownership of Settings issues that have greater impact on CrOS. +abodenha@ for resource allocation consideration.

Sign in to add a comment