New issue
Advanced search Search tips

Issue 857544 link

Starred by 2 users
Status: WontFix
Owner:
kozy@chromium.org
Closed: Aug 21
Cc:
susan.boorgula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

CRDP sometimes hangs on Debugger.setBreakpointByUrl

Reported by dig...@hotmail.com, Jun 28 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/67.0.3396.87 Safari/537.36

Steps to reproduce the problem:
It seems to be a race condition that happens sometimes while setting this breakpoint:
--> Chrome: {"id":14,"method":"Debugger.setBreakpointByUrl","params":{"lineNumber":55,"url":"C:\\fol\\DeR\\Test18\\MyProject\\webpage\\js\\mysite.ts","columnNumber":0,"condition":""}}

I attached a full dump of the CRDP protocol

What is the expected behavior?
CRDP should respond to that request and debugging should continue

What went wrong?
CRDP doesn't respond to that request, it seems that it gets stuck and nothing happens after that

Did this work before? N/A 

Chrome version: 67.0.3396.87  Channel: stable
OS Version: 10.0
Flash Version:
crdp dump.txt
10.1 KB View Download

Comment 1 by dig...@hotmail.com, Jun 28 2018 

We run into this issue on our automated tests which uses the attached project in Visual Studio 2017 15.8.0 Preview 4.0.
You need to set the breakpoint on site.js on Line 54.
The issue is non-deterministic, we don't know exactly how to make this issue reproduce.
TestWebKitDebuggerProject.zip
618 KB Download

Comment 2 by vamshi.kommuri@chromium.org, Jun 29 2018

Labels: Needs-Triage-M67

Comment 3 by susan.boorgula@chromium.org, Jun 29 2018

Cc: susan.boorgula@chromium.org
Labels: Triaged-ET TE-NeedsTriageHelp
digeff@ Thanks for the issue.

This issue seems to be out of scope of triaging at TE end, as this needs to be checked on Visual Studio 2017 as per comment #1.
Hence adding 'TE-NeedsTriageHelp' label and requesting the appropriate team to look into the issue and help in further triaging.

Thanks..

Comment 4 by dig...@hotmail.com, Jul 3 

Do you have an ETA of when will someone be able to look at this issue?

Comment 5 by paulir...@chromium.org, Jul 9

Components: -Platform>DevTools Platform>DevTools>JavaScript
Owner: kozy@chromium.org
Status: Assigned (was: Unconfirmed)
Thanks for the reduction.

Comment 6 by dig...@hotmail.com, Jul 16 

Have you been able to reproduce this issue?

Comment 7 by kozy@chromium.org, Jul 17 

Unfortunately I do not have Visual Studio on my workstation, I took a look to the crdp_dump.text and found some suspicious parts:
1. setting breakpoint in .ts file most likely mistake, setBreakpointByUrl takes JS script url as argument. If your website contains source maps, your harness or DevTools frontend should properly resolve location inside .ts file to location inside JavaScript file using source map.
2. there are two calls to setBreakpointByUrl with the same location in the log with id === 12 and id === 14, protocol returns "Breakpoint at specified location already exists." error as result of second setBreakpointByUrl call and your harness most likely does not process this error properly. Each breakpoint set by this method outlive navigation so there is no need to set it twice using the same location or breakpoint should be removed first.

Comment 8 by kozy@chromium.org, Aug 21

Status: WontFix (was: Assigned)
►

Sign in to add a comment