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

Issue 768703 link

Starred by 1 user
Status: WontFix
Owner:
dpa...@chromium.org
Closed: Dec 2017
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Chrome://settings page turns blank upon multiple refresh on Windows Touch Device.

Reported by aiman.an...@etouch.net, Sep 26 2017 
Chrome Version: 63.0.3223.0 (Official Build)(cohort: 61_Win_100)569732c0a96ec8d0c4c5df7f7012188696c7d37c-refs/heads/master@{#503964}(64-bit) 

OS: Windows(10-Touch Device).

Steps to reproduce:
1.Launch chrome, go to chrome://settings.
2.Refresh the page multiple times using finger touch and observe. 

Actual Result: Chrome://settings page turns blank upon multiple refresh.
Expected Result: Chrome://settings page should not turn blank upon multiple refresh. 

This is regression issue broken in 'M-58' and below per-revision bisect result

Using the per-revision bisect providing the bisect results,
Good Build: 58.0.3016.0(Revision:451404)
Bad Build: 58.0.3017.0(Revision:451476)

You are probably looking for a change made after 451416 (known good), but no later than 451417 (first known bad).

CHANGE-LOG URL:

The script might not always return single CL as suspect as some perf builds might get missing due to failure.

https://chromium.googlesource.com/chromium/src/+log/5ac15460e9aab7b68f858f911b2e4ced8e0aadaa..2d84fd7e2cdb13ae3fbe894319ef828febd14f0e

Suspect: https://chromium.googlesource.com/chromium/src/+/2d84fd7e2cdb13ae3fbe894319ef828febd14f0e

@dpapad: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thank You!
Actual Result.mp4
514 KB View Download
Expected Result.mp4
1.1 MB View Download

Comment 1 by dpa...@chromium.org, Sep 26 2017 

aiman.ansari@etouch.net: Could you provide more information? Specifically:

 - Does this only happen with touch? Can it be reproduced with the mouse?
 - Does it happen on other WebUI pages (chrome://downloads, chrome://history)?
 - Are there any errors in the dev console?

Comment 2 by aiman.an...@etouch.net, Sep 27 2017 

Hi, wrt comment #1,
1. Able to reproduce the above issue with touch only (Unable to reproduce the issue with mouse).
2. Unable to reproduce the above issue for other WebUI pages (chrome://downloads, chrome://history).
3. There are no errors in dev console.

Comment 3 by brucedaw...@chromium.org, Sep 28 2017 

I tried this on 63.0.3225.0 (Official Build) canary 64-bit on a SurfaceBook Pro, using touch, and I could not repro the problem. I tried in tablet mode as well, and I tapped the refresh button with my finger as fast as I could - no good.

The description mentions seeing the bug in 63.0.3223.0 which makes sense for a bug that was reported September 25, 2017. However the bisect mentions M58 and a CL from seven months ago. 

I'm not sure what the 61_Win_100 cohort is. My cohort is 64-bit.

Comment 4 by dpa...@chromium.org, Dec 1 2017

Status: WontFix (was: Assigned)
I am closing this issue since there have been no updates from the reporter, and per #3 it was not reproducible (I don't have a touch Win machine to try myself). Please re-open if it still happens.
►

Sign in to add a comment