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

Issue 681503 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Jan 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: 'Start CPU profiling' (Record) button of 'JavaScript Profiler' section is not working

Reported by jshan...@etouch.net, Jan 16 2017

Issue description

Chrome Version: 57.0.2983.0 (Official Build) (64-bit)266a86c94d34f3c7c3d22ee00624636b801f80d3-refs/heads/master@{#443819}-32/64 bit
OS: Windows(7,8,8.1,10),Mac OS X(10.11.6, 10.12.1)

Steps:
1. Launch Chrome, open Devtools on NTP
2. Go to 'JavaScript Profiler' section from 'Customize and control DevTools' menu list.
3. Click on 'Start CPU profiling' (Record) button and observe.

Actual: Nothing happens after clicking on 'Start CPU profiling' (Record) button i.e it is not working.

Expected: After clicking on 'Start CPU profiling' (Record) button , it should start recording.

This is regression issue, broken in ‘M 57’ and will soon update other info :

Good build:57.0.2980.0
Bad build: 57.0.2982.0


 
Actual_video.mp4
495 KB View Download

Comment 1 by jshan...@etouch.net, Jan 16 2017

Labels: OS-Linux
Note: Issue is also seen on Linux OS
Labels: hasbisect-per-revision ReleaseBlock-Stable
Owner: pfeldman@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build: 57.0.2980.0 (Revision: 443474).
Bad build: 57.0.2982.0 (Revision: 443804).

You are probably looking for a change made after 443787 (known good), but no later than 443788 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/28deea19efca31ffe519dff8e2b986c0c73d7c82..cdd11a51ff07ee98f7611fc15b91cc6dad9345a3

@pfeldman -- 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.
Adding RB Label as this is a recent Regression. Please remove if this is not required.
Thank You.
Labels: Needs-triage-Mobile
Status: Fixed (was: Assigned)
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.
Labels: -Merge-TBD

Sign in to add a comment