Skip to content

Commit 2114ba8

Browse files
author
Isadora Rodopoulos
committed
Follow file name guidelines.
1 parent 5f27bea commit 2114ba8

File tree

3 files changed

+6
-6
lines changed

3 files changed

+6
-6
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ Below are the errors and warning dialog boxes you may encounter while debugging
3232

3333
[Debugger Cannot Display Source Code or Disassembly](../debugger/debugger-cannot-display-source-code-or-disassembly.md)
3434

35-
[Debugging Services Running Out of Memory](../debugger/error-debugging-services-running-out-of-memory.md)
35+
[Debugger Services Running Out of Memory](../debugger/error-debugger-services-no-memory.md)
3636

3737
[Executable for Debugging Session Dialog Box](../debugger/executable-for-debugging-session-dialog-box.md)
3838

docs/debugger/error-debugging-services-running-out-of-memory.md renamed to docs/debugger/error-debugger-services-no-memory.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: "Debugger Services Running Out of Memory | Microsoft Docs"
33
ms.date: "07/10/2019"
44
ms.topic: "troubleshooting"
55
f1_keywords:
6-
- "vs.debug.error.debug_out_of_memory"
6+
- "vs.debug.error.debug_no_memory"
77
dev_langs:
88
- "CSharp"
99
- "VB"
@@ -17,10 +17,10 @@ manager: caslan
1717
ms.workload:
1818
- "multiple"
1919
---
20-
# Debugging Services Running Out of Memory
20+
# Debugger Services Running Out of Memory
2121
The Debugging Services ran out of memory and caused the termination of the debugging session.
2222

23-
### To investigate this error on Windows
23+
## To investigate this error on Windows
2424
- 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).
2525

2626
- 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.

docs/debugger/toc.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -710,8 +710,8 @@
710710
href: cannot-change-value-dialog-box.md
711711
- name: Debugger Cannot Display Source Code or Disassembly
712712
href: debugger-cannot-display-source-code-or-disassembly.md
713-
- name: Debugging Services Running Out of Memory
714-
href: error-debugging-services-running-out-of-memory.md
713+
- name: Debugger Services Running Out of Memory
714+
href: error-debugger-services-no-memory.md
715715
- name: Executable for Debugging Session dialog box
716716
href: executable-for-debugging-session-dialog-box.md
717717
- name: Edit and Continue dialog box (C++)

0 commit comments

Comments
 (0)