You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VSCode: Something odd with language-server local rpc communication: too many new TCP connections for POST /exa.language_server_pb.LanguageServerService/ProgressBars#79
Open
nom3ad opened this issue
Aug 11, 2024
· 0 comments
While trying to debug OOM caused by Codeium language-server process, I came to notice that something is strange with the localhost bound communication between processes. Even though this might have nothing to do with OOM issue, I think this could be a bug that causes some performance damage.
~1000 HTTP calls being made for POST /exa.language_server_pb.LanguageServerService/ProgressBars per minute. (Even when there is no activity in the editor)
This behavior is not found for Vim implementation
No connection reuse for these calls - New TCP connection being made for each HTTP/1.1 requests. This is the case for both VSCode and Vim.
Nitpick:
If it's possible to implement parent-child process communication over stdio instead of TCP, that would be even better.
The text was updated successfully, but these errors were encountered:
nom3ad
changed the title
VSCode: Something odd with LSP communication: too many new TCP connections for POST /exa.language_server_pb.LanguageServerService/ProgressBars
VSCode: Something odd with language-server local rpc communication: too many new TCP connections for POST /exa.language_server_pb.LanguageServerService/ProgressBarsAug 11, 2024
While trying to debug OOM caused by Codeium language-server process, I came to notice that something is strange with the localhost bound communication between processes. Even though this might have nothing to do with OOM issue, I think this could be a bug that causes some performance damage.
wireshark-codeium.zip
POST /exa.language_server_pb.LanguageServerService/ProgressBars
per minute. (Even when there is no activity in the editor)Nitpick:
The text was updated successfully, but these errors were encountered: