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

Issue 682563 link

Starred by 2 users
Status: Fixed
Owner:
pfeldman@chromium.org
Closed: Jan 2017
Cc:
█ hdodda@chromium.org
nyerramilli@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug



Sign in to add a comment

Regression: 'Status' pop overlay of Performance section is seen even after clicking on Clear button.

Reported by jshan...@etouch.net, Jan 19 2017 
Chrome Version:57.0.2986.0 (Official Build) 12c8d70173fc1a04fa588b75be71ab5e80655c60-refs/heads/master@{#444600} 32/64-bit. 
OS:Windows(7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.11.6, 10.12.1)

Steps:
1. Launch Chrome, open devtools on NTP and go to Performance section.
2. Press Esc key to open Console and click on record button then click on Stop or Clear button.
3. Drag the Console drawer extreme upward and observe

Actual:'Status' pop overlay is seen after clicking on Clear button

Expected: 'Status' pop overlay should not be seen after clicking on Clear button 

This is a regression issue, broken in 'M-57', will soon update the other info:

Good Build: 57.0.2984.0
Bad Build: 57.0.2985.0
Actual_video.mp4
372 KB View Download
Expected_video.mp4
599 KB View Download
Actual_result.jpg
153 KB View Download

Comment 1 by hdodda@chromium.org, Jan 19 2017

Cc: hdodda@chromium.org
Labels: hasbisect-per-revision
Owner: pfeldman@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good Build: 57.0.2984.0 (Revision : 443964)
Bad Build: 57.0.2985.0 (Revision : 444244)

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

CHANGELOG 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/b71b7d5967c31b07766cf0ad10be89a9e526ed4a..064f04c82c2f6cd3e9a77703362f9373034c248a

From the CL above, assigning the issue to the concern owner 

@pfeldman - 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.

Review-Url: https://codereview.chromium.org/2637443004

Thanks!

Comment 2 by nyerramilli@chromium.org, Jan 19 2017

Labels: ReleaseBlock-Stable
as this is recent regression adding RBS, please change if required.

Comment 3 by ligim...@chromium.org, Jan 20 2017

Labels: Needs-triage-Mobile

Comment 4 by pfeldman@chromium.org, Jan 23 2017

Status: Fixed (was: Assigned)
Project Member

Comment 5 by blocker...@chrome-infra-auth.iam.gserviceaccount.com, Jan 23 2017

Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-57; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-57 label, otherwise remove Merge-TBD label. Thanks.

Comment 6 by gov...@chromium.org, Jan 24 2017 

pfeldman@, you marked this bug as fixed at #4 but I don't see any change landed. Could you please double check and request a merge to M57. Thank you.

Comment 7 by pfeldman@chromium.org, Jan 24 2017

Labels: -Merge-TBD -Type-Bug-Regression Type-Bug

Comment 8 by ranjitkan@chromium.org, Feb 3 2017 

With respect to the label added: Needs-triage-Mobile, triaged the issue and below are the observations.

Unable to replicate the issue on Mobile device (Tablet and Handset) as the steps provided cannot be followed on it.

Devices Used:
=============
Device Nexus 7 Tablet
Chrome Version: 57.0.2987.9
Android version: 5.0.2/LRX22G

Device: Moto G
Chrome Version: 58.0.2993.0
Android version: 6.0.0/MPB24

Reasons: 
========
1) Dev tool procedure is different than that on mobile and desktop. Need to connect the device externally to the desktop.
►

Sign in to add a comment