Share via

Debugger Services Running Out of Memory

  • Article

Applies to: yesVisual Studio noVisual Studio for Mac

Note

This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here

The Debugging Services ran out of memory and caused the termination of the debugging session.

To investigate this error on Windows

  • You can check the process memory graph in the Diagnostics Tools window to see if the target application is experiencing huge growth in memory. If so, use the Memory Usage tool to diagnose what is the underlying issue, see Analyze memory usage.

  • If the target application does not seem to be consuming a lot of memory, use the Task Manager window to check out memory usage of Visual Studio (devenv.exe), the worker process (msvsmon.exe), or of VS Code (vsdbg.exe/vsdbg-ui.exe) to determine if this is a debugger problem. If the process running out of memory is devenv.exe, consider reducing the number of Visual Studio extensions running.

See also