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

Issue 765865 link

Starred by 1 user
Status: Fixed
Owner:
█ kozyatinskiy@chromium.org
Last visit > 30 days ago
Closed: Oct 2017
Cc:
kkaluri@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Breakpoints get mapped to incorrect lines on the DevTools

Reported by dig...@hotmail.com, Sep 16 2017 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce the problem:
1. Open webpage.html in chrome
2. Go to the sources tab
3. Set breakpoints on the lines that have a comment to set a breakpoint
4. Sometimes it puts the wrong breakpoints already on this step, if that doesn't happen, refresh the page, and the breakpoints will appear on different lines that the lines you set the original breakpoints

What is the expected behavior?
The breakpoints should be applied in the lines I set them too

What went wrong?
It changed my breakpoints, and put them in other lines

Did this work before? N/A 

Chrome version: 60.0.3112.101  Channel: stable
OS Version: 10.0
Flash Version:
breakpoints wrongly mapped.zip
533 bytes Download

Comment 1 by kkaluri@chromium.org, Sep 18 2017

Cc: kkaluri@chromium.org
Labels: M-63 Needs-Milestone OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Windows 10, Ubuntu 14.04 & Mac 10.12.6 with chrome Stable #61.0.3163.91, Canary #63.0.3218.0 and also in earlier version M50-#50.0.2661.0
This is a non-regression issue, hence marking it as untriaged.

Observed breakpoints are changing when i refresh the page.

Attaching the screen-cast for reference.
765865.mp4
907 KB View Download

Comment 2 by allada@chromium.org, Oct 3 2017

Owner: kozyatinskiy@chromium.org
Status: Assigned (was: Untriaged)

Comment 3 by kozyatinskiy@chromium.org, Oct 12 2017

Status: Fixed (was: Assigned)
It's not jumping at line "var m = 4; // Set a breakpoint here" - I believe it was fixed.
And it's not possible to set breakpoints after throw line since we know that this code will never be executed.
Thanks for report!
►

Sign in to add a comment