-
Notifications
You must be signed in to change notification settings - Fork 32.7k
WSL2 mirrored network mode slows VSCode debugging - still not resolved #198429
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
/jsDebugLogs |
Please collect trace logs using the following instructions:
|
I'm not sure this is an issue in the debugger necessarily vs one in WSL, but the log might help indicate what's going wrong |
trace.log added - hope it helps |
This appears to be an upstream issue, we have had a bevy of problems since the latest WSL update with mirrored network mode, e.g. #198285 THere are reports of similar issues outside of debugging, e.g. microsoft/WSL#10844 |
For anyone else coming across this issue, I managed to resolve it by using the following commands (Ubuntu 24.04 with mirrored network mode):
I think it's also related to microsoft/WSL#8171. |
Uh oh!
There was an error while loading. Please reload this page.
Steps to Reproduce:
[wsl2]
memory=8G
networkingMode=mirrored
{
"version": "0.2.0",
"configurations": [
{
"type": "node",
"request": "launch",
"name": "test",
"skipFiles": ["<node_internals>/**"],
"program": "${workspaceFolder}/test.js"
},
]
}
It will take about 1-2 min until the breakpoint is reached. Removing the networkingMode=mirrored from the WSL configuration and restarting the WSL distro will immediately stop at the breakpoint.
The text was updated successfully, but these errors were encountered: