New issue
Advanced search Search tips

Issue 663538 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Nov 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Incorrect line attribution from devtools after pretty-printing source.

Project Member Reported by erikc...@chromium.org, Nov 8 2016

Issue description

Repro steps:
1) """./tools/perf/run_benchmark --browser=canary power.steady_state"""
Once the test starts running, you can Ctr-C out. [Read: I'm too lazy to find the more concise command to download the relevant WPR file]

2) """third_party/catapult/./telemetry/third_party/web-page-replay/replay.py ./tools/perf/page_sets/data/idle_after_loading_stories_002.wpr"""
Start the WPR server.

3) """/Applications/Google\ Chrome\ Canary.app/Contents/MacOS/Google\ Chrome\ Canary --user-data-dir=/tmp/a2 --host-resolver-rules="MAP * 127.0.0.1,EXCLUDE localhost" --ignore-certificate-errors"""

4) Navigate to http://bgr.com

5) Make a timeline recording. Note that this function call repeats every ~30ms
"""
t @ i.js?ver=4.5.3-20160628:1
"""

6) Pretty print i.js. Note that breakpoint on line 1 doesn't trigger.

7) Break on line 178 [search for "eu =", break on "var t = Date.now()"]
Note that this is hit every frame.
 
8) Make another timeline recording. Note that line 1 is still called out.

Cc: paulir...@chromium.org
Owner: alph@chromium.org
thx for the detailed repro steps.

Comment 3 by alph@chromium.org, Nov 23 2016

Status: WontFix (was: Assigned)
Can't repro. Perhaps has been fixed recently.

Sign in to add a comment