Skip to content

Commit ecc1467

Browse files
committed
edits
1 parent ee517ff commit ecc1467

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/debugger/debug-64-bit-applications.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -24,16 +24,16 @@ You might see one of the following errors:
2424
- "A 64-bit debugging operation is taking longer than expected." or
2525
- "A debugger operation is taking longer than expected."
2626

27-
In these scenarios, Visual Studio sent a request to msvsmon.exe, and it has taken a long time for the result of that request to come back.
27+
In these scenarios, Visual Studio sent a request to msvsmon.exe, and it's taken a long time for the result of that request to come back.
2828

2929
The most common causes for this error are:
3030

31-
- You have networking security software installed on your computer that has caused the networking stack to be unreliable, and it has dropped packets going over `localhost`. Try disabling all network security software and see whether this resolves it. If so, report to your network security software vendor that the software is interfering with `localhost` traffic. This shouldn't occur with Visual Studio 2019 and later, because those versions don't use sockets for this communication.
31+
- You have networking security software installed on your computer that has caused the networking stack to be unreliable, and it's dropped packets going over `localhost`. Try disabling all network security software and see whether this resolves it. If so, report to your network security software vendor that the software is interfering with `localhost` traffic. This shouldn't occur with Visual Studio 2019 and later, because those versions don't use sockets for this communication.
3232

3333
- You're running into an issue where Visual Studio becomes unresponsive, or other performance problem. If the problem happens regularly, you can [collect dumps](../debugger/using-dump-files.md) of Visual Studio (devenv.exe) and the worker process (msvsmon.exe) and send them to Microsoft. For information about reporting a problem, see [How to Report a Problem with Visual Studio](../ide/how-to-report-a-problem-with-visual-studio.md).
3434

3535
::: moniker range=">= vs-2022"
36-
- If you are using a version of Visual Studio prior to Visual Studio 2022, you may be trying to debug a 64-bit application while running in the 32-bit Visual Studio process. To resolve, follow instructions to [debug a 64-bit application](/previous-versions/visualstudio/visual-studio-2017/debugger/debug-64-bit-applications?view=vs-2017&preserve-view=true).
36+
- If you're using a version of Visual Studio prior to Visual Studio 2022, you may be trying to debug a 64-bit application while running in the 32-bit Visual Studio process. To resolve, follow instructions to [debug a 64-bit application](/previous-versions/visualstudio/visual-studio-2017/debugger/debug-64-bit-applications?view=vs-2017&preserve-view=true).
3737
::: moniker-end
3838

3939
::: moniker range="<= vs-2019"

0 commit comments

Comments
 (0)