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
### Reproduction steps
1. Start the Ruby LSP with VS Code
2. Install VIM plugin
3. Open a Ruby file in a large Rails project (1000k+ files)
4. Insert a charachar with `INSERT` mode
5. The second key stroke takes a few seconds to appear. Switching to normal mode with `ESC` takes a few seconds too.
```ruby
gem 'brakeman', '~> 5.4', require: false
gem 'rubocop', '~> 1.51', require: false
I can see the extension host becomes unresponsive when RubyLSP runs brakeman and rubocop. (CPU 100%).
The text was updated successfully, but these errors were encountered:
erickguan
added
bug
Something isn't working
vscode
This pull request should be included in the VS Code extension's release notes
labels
Nov 28, 2024
Thank you for the bug report! I'm a bit confused though. We don't run brakeman in the Ruby LSP, unless you have some add-on for brakeman.
Also, I'm not sure how the Vim plugin could be impacting this. It's VS Code itself that decides when to trigger code action providers. FWIW, I use the Vim plugin myself.
Also, I'm not sure how the Vim plugin could be impacting this. It's VS Code itself that decides when to trigger code action providers. FWIW, I use the Vim plugin myself.
Thanks for your time! From your VIM setup, I was able to find my mistake when debugging again. This is on me. I have an extension fnando.linter runs brakeman and then rubocop.
Name: Linter
Id: fnando.linter
Description: An extension for VSCode that provides linting for multiple languages in on package.
Version: 0.0.19
Publisher: Nando Vieira
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=fnando.linter
I used it for YAMLint but failed to capture its existence when I debugged this performance.
When I disabled RubyLSP, the performance was slower but okay. When I enabled RubyLSP, two extensions hogged my CPU.
@erickguan might you have some config in a .vimrc or similar that the extension is picking up?
@andyw8 Thanks for your reply. It's my environmental contamination (M2 Pro).
ruby-lsp process on save reaches around 30-50% peak.
Description
Ruby LSP Information
User
I can see the extension host becomes unresponsive when RubyLSP runs brakeman and rubocop. (CPU 100%).
The text was updated successfully, but these errors were encountered: