Language server crashes after a few seconds

After a few seconds, the language server crashes every time. When I hover over function names, I get the help text only for a few seconds. When I try again after a couple of seconds, it only shows Loading....

I'm using the extension in a x86 Linux development container on my MacBook (Apple chip).

Output:

[Error - 7:35:41 AM] Client R Language Server: connection to server is erroring.
read ECONNRESET
[Error - 7:35:41 AM] Client R Language Server: connection to server is erroring.
read ECONNRESET
R Language Server (2347) exited from signal SIGKILL
[Error - 7:35:41 AM] Client R Language Server: connection to server is erroring.
Cannot call write after a stream was destroyed
[Error - 7:35:41 AM] Client R Language Server: connection to server is erroring.
Cannot call write after a stream was destroyed
[Error - 7:35:41 AM] Client R Language Server: connection to server is erroring.
Cannot call write after a stream was destroyed
[Error - 7:35:41 AM] Updating trace failed with error
Error: Cannot call write after a stream was destroyed
    at _write (node:internal/streams/writable:489:11)
    at Socket.Writable.write (node:internal/streams/writable:508:10)
    at /home/vscode/.vscode-server/extensions/reditorsupport.r-2.8.4/dist/extension.js:2:518517
    at new Promise (<anonymous>)
    at s.write (/home/vscode/.vscode-server/extensions/reditorsupport.r-2.8.4/dist/extension.js:2:518435)
    at E.doWrite (/home/vscode/.vscode-server/extensions/reditorsupport.r-2.8.4/dist/extension.js:2:506035)
    at /home/vscode/.vscode-server/extensions/reditorsupport.r-2.8.4/dist/extension.js:2:505930
    at runNextTicks (node:internal/process/task_queues:60:5)
    at processImmediate (node:internal/timers:454:9)
[Error - 7:35:41 AM] Client R Language Server: connection to server is erroring.
Cannot call write after a stream was destroyed
[Error - 7:35:41 AM] Stopping server failed
  Message: Cannot call write after a stream was destroyed
  Code: -32099 

or

R Language Server (4463) exited from signal SIGKILL
[Error - 7:47:01 AM] Client R Language Server: connection to server is erroring.
This socket has been ended by the other party
[Error - 7:47:01 AM] Request textDocument/hover failed.
  Message: This socket has been ended by the other party
  Code: -32099 
[Error - 7:47:02 AM] Client R Language Server: connection to server is erroring.
This socket has been ended by the other party
[Error - 7:47:02 AM] Request textDocument/hover failed.
  Message: This socket has been ended by the other party
  Code: -32099 
[Error - 7:47:02 AM] Client R Language Server: connection to server is erroring.
This socket has been ended by the other party
[Error - 7:47:02 AM] Request textDocument/hover failed.
  Message: This socket has been ended by the other party
  Code: -32099 
[Error - 7:47:02 AM] Client R Language Server: connection to server is erroring.
This socket has been ended by the other party
[Error - 7:47:02 AM] Request textDocument/hover failed.
  Message: This socket has been ended by the other party
  Code: -32099 
[Error - 7:47:02 AM] Client R Language Server: connection to server is erroring.
This socket has been ended by the other party
[Error - 7:47:02 AM] Client R Language Server: connection to server is erroring.
This socket has been ended by the other party
[Error - 7:47:02 AM] Client R Language Server: connection to server is erroring.
This socket has been ended by the other party
[Error - 7:47:02 AM] Stopping server failed
  Message: This socket has been ended by the other party
  Code: -32099 

Start by reproducing the crash in the reported x86 Linux development container on an Apple-chip Mac, using hover requests against the R Language Server. Inspect the logged SIGKILL, ECONNRESET, and destroyed-stream errors, including the referenced dist/extension.js path. Done means the server stays connected and hover help continues working after several seconds.