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

Issue 725467 link

Starred by 1 user
Status: WontFix
Owner:
█ phulce@chromium.org
Last visit > 30 days ago
Closed: May 2017
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Audit does not get started after killing page and clicking on 'Run audit' button.

Reported by db...@etouch.net, May 23 2017 
Chrome Version: 60.0.3108.0 Revision e17728ae5d18e371378473c0b4637940f95c3967-refs/heads/master@{#473773}
OS: Windows(7,8,8.1), Linux(14.04 LTS), Mac(10.11.6, 10.12.3)

What steps will reproduce the problem?
(1) Launch chrome, open dev tools window navigate to Audits section.
(2) Type chrome://kill in omnibox,click on 'Perform an audit' button then click on 'Run audit' button.
(3) Observe.

Actual: Audit does not get started after clicking on 'Run audit' button and after reloading page About:blank page opens

Expected: Audit should gets started.

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

Good Build:60.0.3107.0
Bad Build: 60.0.3108.0
Actual_Audits.mp4
744 KB View Download
Expected_Audits.mp4
713 KB View Download

Comment 1 by rbasuvula@chromium.org, May 23 2017

Cc: rbasuvula@chromium.org
Labels: hasbisect-per-revision
Owner: phulce@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build:60.0.3107.0 (Revision:473482).
Bad build:60.0.3108.0 (Revision:473773).

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

CHANGE-LOG URL:
---------------
https://chromium.googlesource.com/chromium/src/+log/55c71f0ff307dfc3b3e561a2f72e90bb3df05393..a2e8568a2bf96f91c458ab39b0ffa449cebd50b6

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

@phulce: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Review-Url:https://codereview.chromium.org/2895913003
Note :Able to reproduce the issue in Win 10.0,Ubuntu 14.04 & Mac 10.12.3 and Able to reproduce in latest Canary #60.0.3108.0

Comment 2 by phulce@chromium.org, May 23 2017

Status: WontFix (was: Assigned)
Auditing a killed page is not possible and both behaviors are consistent with the rest of DevTools panes being non-functional after the target has been closed (Performance and console both hang in similar manners after the page is killed).

Comment 3 by db...@etouch.net, May 24 2017 

With respect to comment 2:

After typing chrome://kill in omnibox and reloading page about:blank page is seen. original page should be seen after reloading page. 

Thank you
►

Sign in to add a comment