code 132 or "The window is not responding" when connecting to local network SSH hosts

Does this issue occur when all extensions are disabled?: Yes/No

- VS Code Version: 1.130.0
- OS Version: CachyOS (7.1.5-1-cachyos)

Steps to Reproduce:

When connecting to a local network host via SSH, VS Code eventually hangs anywhere from a few minutes to within 30 minutes. Once this happens, the window becomes unresponsive and cannot be closed normally. Eventually, either a `code 132` crash is reported or the message **"The window is not responding"** appears.

This issue only occurs when connecting to hosts on the local network. It does not occur when connecting to external SSH servers, and I have been experiencing this issue consistently for several months.

1. Before the crash (window stuck in an infinite loading state)

2. After the loading stops (code 132 or "The window is not responding" appears)

Start by reproducing the hang with a local-network SSH host in VS Code 1.130.0 on CachyOS, comparing it with an external SSH server and with extensions disabled. Use the loading state, unresponsive-window message, and code 132 crash as the failure criteria; done means the local SSH connection remains usable without the window hanging or crashing.

Written by the indexing model from the issue text.