Issue metadata
Sign in to add a comment
|
Sources panel keeps opening up irrelevant files
Reported by
russ.a.b...@gmail.com,
Jul 31
|
||||||||||||||||||||||
Issue description
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.75 Safari/537.36
Steps to reproduce the problem:
1. open a js file or make a new snippet
2. place a break point
3. run code
What is the expected behavior?
The debugger should step through MY code in the js file or the snippet.
What went wrong?
It keeps opening up files and scripts that belong to chrome extensions. Even something as simple console.log() opens up files that have NOTHING to do with what I am trying to debug. it tries to step through EVERY line of code, even system level code.
For example, I created a new snippet consisting of one line of code:
console.log("hello");
stepping through one line at at time opened up:
/_/scs/social-static/_/js/k=boq.NotificationsOgbUi.en.LebJg7r5BNQ.O/am=AAEABAEBBA/rt=j/d=1/excm=home,_b,_tp/ed=1/rs=AGLTcCN5U8nsOR2NB07Wl7yDPApQkYC1CQ/m=_b,_tp
Did this work before? Yes This has been getting progressively worse over the last few months.
Chrome version: 68.0.3440.75 Channel: beta
OS Version: 10.0
Flash Version:
My devtools is effectively inoperable as of this version.
,
Aug 2
Unable to reproduce the issue on Win-10 using chrome latest stable #68.0.3440.84 and latest canary #70.0.3508.0.
Attached a screen cast for reference.
Following are the steps followed to reproduce the issue.
------------
1. Made a new snippet by using a single line of code i.e console.log("hello");
2. Placed a break point at that line of code.
3. Ran code
4. Observed that debugger stepped through the code in snippet.
russ.a.bain@ - Could you please check the issue on latest stable #68.0.3440.84 by creating a new profile without any apps and extensions and please let us know if the issue still persists or not. Also please check the attached screen cast and please let us know if anything missed from our end. If possible please provide a sample test file/url to test the issue from TE-end.
Thanks...!!
,
Aug 2
Thank you krajshree@. Setting up a custom user profile and configuring my IDE to open up that profile seems to have solved that problem. I can direct my IDE to not open any library files in its native debugger, but it seems that Chrome cannot be so directed? Not looking to start a debate here. Just expressing my 2 cents: Given the tiny proportion of the dev population that actually needs to look into library files or extension files, wouldn't it make more sense to make the default behavior to NOT do that? Thank you for your help in solving my problem!
,
Aug 2
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 3
As per comment #3, please let us know if the issue can be closed from our end. Thanks...!!
,
Aug 3
Yes,please close it.
,
Aug 3
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 6
As per comment #6, closing the issue as wontFix. Thanks...!! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by swarnasree.mukkala@chromium.org
, Aug 1