Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
vsdbg memory leak
See original GitHub issueVisual Studio is using the binary vsdbg to attach the debug session inside a container.
A long running debug session with few thousand debug output lines,
vsdbg will consume an high amount of memory.
The memory grow is linear and reaches >800MB.
A workaround would be to detach and attach Visual Studio to the running debug session.
This issue i experience already in 2019 and it is persistent in the current versions: Visual Studio 2019 16.6.5 mcr.microsoft.com/dotnet/core/sdk:3.1 mcr.microsoft.com/dotnet/core/aspnet:3.1 win10 2004, wsl2 docker 2.3.0.4
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I had now a long debug session over 2-3 days.
There after 2-4 days the user-debug output stopped and only
The thread 0xXX has exited with code 0 (0x0).got printed out over view houres.I detached visiual studio from the debug session and
vsdbginside the container got closed. The container fall from 870MB memory usage to 160MB.After i attached a new debug session to the container, user-debug output got generated and the app tried to reconnect and made worked/responded.
It is most likely a thread starvation inside the container from
vsdbgthx, I will close the issue then.