"Loaded scripts" pane is empty

[provegard]

I have created an application that allows me to debug Nashorn scripts running in the JVM using Chrome or VS code.

For some reason, the Loaded scripts pane is empty:

I have been able to see loaded scripts before, but I'm not sure what happened when they disappeared.

Additional information:

• Debugger for Chrome has version 4.2.1 (apologies if this is the wrong repo to create an issue in, but since #159 is here I figured I'm in the right place).

• I can debug a script, i.e. the debugger stops on a breakpoint and I can step and inspect variables, evaluate expressions etc.

• If I type .scripts in the debug console, I get a script listing:

  › eval:///Script5/eval/961160488
  › eval:///ScriptRecompilation1/eval/1302227152
  › file:///c:/kod/projects/nashorn-debugging/debugee/scripts/script.js (c:\kod\projects\nashorn-debugging\debugee\scripts\script.js)

• I have tried downgrading Debugger for Chrome all the way to 3.4.0 without luck.

• I have tried to use an older version of my application that should work. No luck.

• In vscode-chrome-debug.txt, I see loadedSource events, which I think are related to the Loaded Scripts pane:

To client: {"seq":0,"type":"event","event":"loadedSource","body":{"reason":"new","source":{"name":"script.js","path":"file:///c:/kod/projects/nashorn-debugging/debugee/scripts/script.js","sourceReference":1001}}}

• I have tried to debug this extension, but I couldn't set breakpoints because ironically the Loaded scripts page was empty...
• If I debug a file-based web page running in Chrome (i.e. I let VS code launch Chrome), scripts do appear in the Loaded scripts page, so the problem is clearly contextual.

What could possible cause the pane to be empty?

[roblourens]

If you force the node-debug extension to activate, e.g. by running the "Debug: Toggle Skipping This File" command, then debug chrome, then it works.

@weinand I guess we just need to change node-debug to activate when Chrome debugging starts? Will this tree live in vscode at some point?

[weinand]

@roblourens yep, moving the tree to the VS Code is on the 6 month roadmap.

[provegard]

@roblourens Thanks, activating the extension manually worked!

@weinand Is this not a bug then? From a user's perspective it appears to be a regression, since the pane has worked before. If I have inadvertently activated the extension before, I have no clue how... :)

[weinand]

The "loaded scripts view" is no longer contributed by node-debug but is a built-in feature of VS Code.
If this issue still reproduces, please file a bug against VS Code.