Merge pull request #4986 from isadorasophia/isgarcia/out-of-memory-doc

Add documentation for "Debugging Services Running Out of Memory"

Author: ShannonLeavitt

docs/debugger/debugging-errors-and-warning-dialog-boxes.md

@@ -31,6 +31,8 @@ Below are the errors and warning dialog boxes you may encounter while debugging
  [Cannot Change Value Dialog Box](../debugger/cannot-change-value-dialog-box.md)
 
  [Debugger Cannot Display Source Code or Disassembly](../debugger/debugger-cannot-display-source-code-or-disassembly.md)
+ 
+ [Debugger Services Running Out of Memory](../debugger/error-debugger-services-no-memory.md)
 
  [Executable for Debugging Session Dialog Box](../debugger/executable-for-debugging-session-dialog-box.md)
 

docs/debugger/error-debugger-services-no-memory.md

@@ -0,0 +1,30 @@
+---
+title: "Debugger Services Running Out of Memory | Microsoft Docs"
+ms.date: "07/10/2019"
+ms.topic: "troubleshooting"
+f1_keywords:
+  - "vs.debug.error.debug_no_memory"
+dev_langs:
+  - "CSharp"
+  - "VB"
+  - "FSharp"
+  - "C++"
+helpviewer_keywords:
+  - "debugger"
+author: "isadorasophia"
+ms.author: "isgarcia"
+manager: caslan
+ms.workload:
+  - "multiple"
+---
+# Debugger Services Running Out of Memory
+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](../profiling/memory-usage.md).
+
+- 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
+- [Blog post: Analyze CPU and Memory while Debugging](https://devblogs.microsoft.com/visualstudio/analyze-cpu-memory-while-debugging/)
+- [About Memory Management](/windows/win32/memory/about-memory-management)

docs/debugger/toc.yml

@@ -710,6 +710,8 @@
         href: cannot-change-value-dialog-box.md
       - name: Debugger Cannot Display Source Code or Disassembly
         href: debugger-cannot-display-source-code-or-disassembly.md
+      - name: Debugger Services Running Out of Memory
+        href: error-debugger-services-no-memory.md
       - name: Executable for Debugging Session dialog box
         href: executable-for-debugging-session-dialog-box.md
       - name: Edit and Continue dialog box (C++)