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
{{ message }}
This repository has been archived by the owner on Jun 15, 2023. It is now read-only.
Sometimes LSP sends many didChange events even though I barely change any file. The backend I use, clojure-lsp, does non-trivial analysis on changed files and thus consumes all my CPU for no good reason. Here is an example from its log of what it received:
It is not clojure-lsp issue because when I use it from VS Code, it works just fine. So the cause seems indeed to be that LSP sends too many of these didChange events in a short time window.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sometimes LSP sends many
didChange
events even though I barely change any file. The backend I use, clojure-lsp, does non-trivial analysis on changed files and thus consumes all my CPU for no good reason. Here is an example from its log of what it received:It is not clojure-lsp issue because when I use it from VS Code, it works just fine. So the cause seems indeed to be that LSP sends too many of these didChange events in a short time window.
The text was updated successfully, but these errors were encountered: