Skip to content
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

WSL2 mirrored network mode slows VSCode debugging - still not resolved #198429

Closed
aknuth opened this issue Nov 16, 2023 · 6 comments
Closed

WSL2 mirrored network mode slows VSCode debugging - still not resolved #198429

aknuth opened this issue Nov 16, 2023 · 6 comments
Assignees
Labels
*out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)

Comments

@aknuth
Copy link

aknuth commented Nov 16, 2023

  • VS Code Version: 1.84.2
  • OS Version: 10.0.22621.2715
  • wsl Version: 2.0.9.0

Steps to Reproduce:

  1. create wsl config like this
    [wsl2]
    memory=8G
    networkingMode=mirrored
  2. start your WSL2 distribution (actually I took ubuntu 22.04)
  3. install node.js (e.g. by using nvm - curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.5/install.sh | bash && nvm install --lts && nvm use --lts)
  4. attach your Windows VSCode to a remote WSL folder and create a simple test.js file with one line of code -> console.log('test')
  5. create a launch config like
    {
    "version": "0.2.0",
    "configurations": [
    {
    "type": "node",
    "request": "launch",
    "name": "test",
    "skipFiles": ["<node_internals>/**"],
    "program": "${workspaceFolder}/test.js"
    },
    ]
    }
  6. create a breakpoint in test.js and start debugging 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.
@aknuth aknuth changed the title WSL2 mirrored network mode slows VSCode - still not resolved WSL2 mirrored network mode slows VSCode debugging - still not resolved Nov 16, 2023
@roblourens roblourens assigned connor4312 and unassigned roblourens Nov 16, 2023
@connor4312
Copy link
Member

/jsDebugLogs

@vscodenpa
Copy link

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 [email protected]

@vscodenpa vscodenpa added the info-needed Issue requires more information from poster label Nov 16, 2023
@connor4312
Copy link
Member

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

@aknuth
Copy link
Author

aknuth commented Nov 16, 2023

trace.log added - hope it helps
vscode-debugadapter-262f3b82.json.gz

@zed76r
Copy link

zed76r commented Nov 20, 2023

@connor4312
Copy link
Member

connor4312 commented Nov 30, 2023

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

@connor4312 connor4312 added upstream Issue identified as 'upstream' component related (exists outside of VS Code) *out-of-scope Posted issue is not in scope of VS Code and removed info-needed Issue requires more information from poster labels Nov 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
*out-of-scope Posted issue is not in scope of VS Code upstream Issue identified as 'upstream' component related (exists outside of VS Code)
Projects
None yet
Development

No branches or pull requests

5 participants