Chrome Developer Tool: html script is an empty (in the original) debugging tutorial

Question

I am performing C hrome debugging using NetBeans and Google Chrome. Everything, including extensions, seems to work correctly, but when I go to the Use the Debugger section, I don't see the html code inserting a breakpoint.

After selecting the pop-up viewport in the browser, it opens in the console without displaying anything, Elements shows popup.html with the added images. When I go to Sources, the popup.html file can be opened, but the only line, line 1, is empty. If I open the js file, the js file will be there and can be edited (renamed).

I'm sorry - maybe something basic, but I'm not very good at it. I tried rebooting and updating everything.

FOLLOW-UP: by entering location.reload(true) at the console prompt, the popup.html file became visible as a source! What for? I do not know.

Hope this saves someone the whole day when I stumbled.

Answer 1

This is apparently a known issue with Chromium DevTools. Basically, HTML and other non-script content are already cleared before DevTools opens, and there is no reliable way to return it. Refreshing a page using DevTools opens a “fix” problem.

Answer 2

I had this problem and I just found that disabling "Enable Javascript Source Cards" from the inspector settings window (F1) enabled it

I recreated my js.map, re-set the parameter, and the source was still available.

So I think that my problem was that I was running unminified js (dev settings), but the map (built for prod settings) was still outdated.

Answer 3

In my case, I could not access the console, as the tab also showed a blank page. My solution is to use the CTRL + SHIFT + i combination with the focus of an empty debugger, then type parent.location.reload(true) in the pop-up debugger console.

Answer 4

in my case the order helped

1. close blank tab in sources
2. close development tools
3. open source tools
4. open the tab in the sources (it is still empty)
5. refresh the page

Answer 5

In my case, there was an extension in chrome that caused the debugger to give an empty index page in the "no domain" section of the debugger. After disabling all non-essential extensions in chrome, the debugger again showed the correct source.

Answer 6

I noticed that some serious problems with javascript cause such problems. In my case, I mistakenly rewrote the entire document due to a typo.

If you get a blank html page in the Chromium WebTools debugger, take a good look at your javascript to make sure this doesn't do anything weird.

Answer 7

I fixed my problem using a completely new session with the command line argument "--user-data-dir" and disabling "Enable Javascript Source Cards". My code shows itself well in the Firefox debugger, so it looks like it is due to a Chrome error.

Answer 8

I had the same problem. Even the page refresh did not work.

The transition chrome://help and browser update + reboot worked for me.

You can also update Chrome through the menu:

Answer 9

In my case, this happened suddenly, after being infected by malware, and I reset my browser - the remote cache / appdata.

Solution: remove the extension that may affect Js in my case

I uninstalled / disabled the bottom extension and worked https://chrome.google.com/webstore/detail/quick-javascript-switcher/geddoclleiomckbhadiaipdggiiccfje?hl=en

strange, because before I erase this add-on without any problems, I think it looks like CPR. :)

Answer 10

In my case, I had gulp with a browser for several days. I jumped gulp and solved the problem.

Answer 11

I also had this problem, when I had a huge java-script file, I had this line

  points.push({ location: new google.maps.LatLng(46.5376919, 4.5425704), date : "5/8/2017 5:11:00 PM", free : true }); 

in a for loop and it counted 3000 elements, so the script file became large, and in chrome sources this file was empty. (I think I hit some restrictions)

After the file was reduced, deleting up to 100 elements, it worked fine.

Answer 12

Dev Tools (F12) → Inspector Settings Window (F1) → Restoring default settings and rebooting [button below] works for me!