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

Issue 722244 link

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



Sign in to add a comment

Regression : Weird blue traces of 'Break point' icon is seen in devtools.

Reported by rp...@etouch.net, May 15 2017 
Version: 60.0.3100.0 f472642fd6c20b63b0f1a2f62564f2aad56f4be3-refs/heads/master@{#471639}
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.11.6,10.12.1)

What steps will reproduce the problem?
1. Launch chrome, navigate to NTP and open devtools
2. Now go to 'Sources' section and press 'Ctrl + P' and select a file (Ex. rs=ACT900h...)
3. Now click on line no. to add 'Break points' and observe

Actual: Weird blue traces of 'Break point' icon is seen in code area after clicking on line no. 
Expected: Weird blue traces of 'Break point' icon should not be seen in code area after clicking on line no. 

This is regression issue, broken in ‘M 57’ and will soon update other info :
Good build:57.0.2939.0
Bad build: 57.0.2940.0
Actual_video.mp4
933 KB View Download
Expected_video.mp4
903 KB View Download

Comment 1 by jmukthavaram@chromium.org, May 15 2017

Cc: jmukthavaram@chromium.org
Labels: hasbisect-per-revision
Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce this issue on windows 7, Mac 10.11.4,Linux Ubuntu 14.04 with Chrome Canary-60.0.3099.0.
Manual Bisect:
------------
Good build:57.0.2939.0-Revision-435817
Bad build: 57.0.2940.0-Revision-436137

Per revision Bisect Tool Info:
----------------------------
You are probably looking for a change made after 436042 (known good), but no later than 436043 (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/e7fa62c57b78c4c0433f7570fe34ad16a323db47..225f2381b9e5184fc8edd59baacca0f1d74d7158

kozyatinskiy@,Kindly take a look and please help us to reassign this issue to a right owner if not with respect to this change.

Thanks.!

Comment 2 by kozyatinskiy@chromium.org, May 16 2017

Status: WontFix (was: Assigned)
Thanks for bisect! It's not an issue - it's feature. From 57 we show inline breakpoints for our users for lines where more then one breakable location exists to allow them setting breakpoint in arrow functions.

Comment 3 by paulir...@chromium.org, May 16 2017 

btw rpise.. if it helps... I'd say DevTools team doesn't normally need the "expected_video" in our bug reports. Most of the issues etouch reports are very clear and we understand the bug.

I bet there are some cases where providing the expected_video would be helpful, but in general I'd say you can omit it, and save some time. :)

Comment 4 by rp...@etouch.net, May 17 2017 

With response to comment #3:
@paulirish : Thanks for the comment,would definitely work on your suggestions.
►

Sign in to add a comment