Unbound breakpoint

[cyj8b]

JavaScript breakpoint Unbound。
This issue occurs in 1.8x ,eg 1.85.2，but breakpoint takes effect in 1.7x ,eg 1.75.1
Does this issue occur when all extensions are disabled?: Yes

• VS Code Version: 1.85.2
• OS Version: window 10

Steps to Reproduce:

1. create a new project by cocos creator 2.3.4
2. developer of menu->vs code workflow -> add Chrome Debug config
3. set breakpoint in vscode
4. run project in vscode
5. Breakpoints will not be hit

[vscodenpa]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.86.2. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

[cyj8b]

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.86.2. Please try upgrading to the latest version and checking whether this issue remains.

Happy Coding!

The problem still exists when I switch to 1.86.2

[roblourens]

/jsDebugLogs

[vscodenpa]

Please collect trace logs using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.

⚠️ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to connor@xbox.com

[sekhuat]

I faced same issue and I had attached the trance logs here. The same node js project all the while the breakpoint is working fine. Only these few days it suddenly stop working. Please help, my VS Code version is 1.86.2.
vscode-debugadapter-a1a520bd.json.gz

[cyj8b]

Please collect trace logs using the following instructions:

If you're able to, add "trace": true to your launch.json and reproduce the issue. The location of the log file on your disk will be written to the Debug Console. Share that with us.
⚠️ This log file will not contain source code, but will contain file paths. You can drop it into https://microsoft.github.io/vscode-pwa-analyzer/index.html to see what it contains. If you'd rather not share the log publicly, you can email it to connor@xbox.com

vscode-debugadapter-7cbd9e21.json.gz

[cyj8b]

I faced same issue and I had attached the trance logs here. The same node js project all the while the breakpoint is working fine. Only these few days it suddenly stop working. Please help. vscode-debugadapter-a1a520bd.json.gz

VScode may have been automatically updated to the latest version，eg: 1.86.2 or 1.8x

[sekhuat]

I faced same issue and I had attached the trance logs here. The same node js project all the while the breakpoint is working fine. Only these few days it suddenly stop working. Please help. vscode-debugadapter-a1a520bd.json.gz

VScode may have been automatically updated to the latest version，eg: 1.86.2 or 1.8x

My existing VS Code version is 1.86.2.

[cyj8b]

I faced same issue and I had attached the trance logs here. The same node js project all the while the breakpoint is working fine. Only these few days it suddenly stop working. Please help. vscode-debugadapter-a1a520bd.json.gz

VScode may have been automatically updated to the latest version，eg: 1.86.2 or 1.8x

My existing VS Code version is 1.86.2.

That's right。 The issue I encountered also occurred in version 1.8x。
So I suspect this issue occurred in version 1.8x。

[connor4312]

It doesn't look like the script you set breakpoints in is being loaded in the program you're debugging, or your build process is not emitting sourcemaps for it.

[cyj8b]

It doesn't look like the script you set breakpoints in is being loaded in the program you're debugging, or your build process is not emitting sourcemaps for it.

But it runs ok when I switch to verson 1.7x of vscode with the same project setting.

[connor4312]

Could you please collect a trace log on a version of VS Code that works for you so I can see the difference?

[cyj8b]

Could you please collect a trace log on a version of VS Code that works for you so I can see the difference?

Unbound breakpoint log:
1.86.2_vscode-debugadapter-6fb774ca.json.gz

Capture breakpoint log:
1.75.1_vscode-debugadapter-97ec8ff1.json.gz

[kbeeveer46]

I'm having the same issue in a React project using the SharePoint Framework (SPFx). When this happened last time it was from a bug in a release and reverting to the previous release fixed it and eventually fixed when the next release came out. I tried going back several releases and even to the latest 1.7 release and can't get my breakpoints to work. I've been working on this project several years and haven't changed my launch file. I'm not sure when the problem started because I just came back from taking a month break from the project.

I also tried using the launch file recommended by Microsoft but still can't get the breakpoints to turn red. They are just a black circle that is not filled in. https://learn.microsoft.com/en-us/sharepoint/dev/spfx/debug-in-vscode

{
            "name": "Chrome Hosted workbench",
            "type": "chrome",
            "request": "launch",
            "url": "https://xxxxx.sharepoint.com/sites/ClientPortalQA/_layouts/15/workbench.aspx?debug=true&noredir=true&debugManifestsFile=https://localhost:4321/temp/manifests.js",
            "webRoot": "${workspaceRoot}",
            "sourceMaps": true,
            "sourceMapPathOverrides": {
                "webpack:///.././src/*": "${webRoot}/src/*",
                "webpack:///../../../src/*": "${webRoot}/src/*",
                "webpack:///../../../../src/*": "${webRoot}/src/*",
                "webpack:///../../../../../src/*": "${webRoot}/src/*"
            },
            "runtimeArgs": [
                "--remote-debugging-port=9222"
            ],
            "skipFiles": [
                "<node_internals>/**",
                "${webRoot}/node_modules/**/*.js"
            ],
            "resolveSourceMapLocations": [
                "${workspaceFolder}/**",
                "!**/node_modules/**"
            ]
        }

[kbeeveer46]

Disregard my comment above. The issue was caused by the spfx-fast-serve-helpers package that I upgraded. When I downgraded to the previous version my breakpoints work.

[connor4312]

Much appreciated, fixed in the nightly build out in a couple hrs.

[andreamah]

Hi @cyj8b, can you verify that this is fixed in the latest insiders build? thanks!

[TylerLeonhardt]

@connor4312 can we get some verification steps just in case?

[connor4312]

I don't have good repro steps unfortunately, it's better if the OP is able to verify this