Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ncl: ram usage on completion in neovim #66

Open
sedlund opened this issue Mar 21, 2024 · 0 comments
Open

ncl: ram usage on completion in neovim #66

sedlund opened this issue Mar 21, 2024 · 0 comments

Comments

@sedlund
Copy link

sedlund commented Mar 21, 2024

Describe the bug

When using nls in neovim (lunarvim) tabbing through completions continually causes ram usage to grow infinitely

To Reproduce
This is a minimal reproducer using tab to cycle through completions, it does the same if you are searching through completions growing infinitely larger.

d=ncl-ram-usage; mkdir $d && cd $d
nix flake init -t github:tweag/tf-ncl#hello-tf

in flake.nix:

use the latest nickel / ncl release

tf-ncl.inputs.nickel.follows = "nickel";

add github profider

nix flake update
git init # required for lvim to autostart lsp
git add flake.nix
echo -e "use flake\nlink-schema" > .envrc
direnv allow

Add syntax highlighting plugin for neovim:

lvim.plugins = {
  {
    "nickel-lang/vim-nickel",
  },
}

Setup nls in lunarvim (neovim) config.lua:

require('lspconfig')["nickel_ls"].setup {}

if using mason to autoconfigure lsp's disable it for nickel

vim.list_extend(lvim.lsp.automatic_configuration.skipped_servers, { "nickel_ls" })

lvim main.ncl

tf-ncl-nls-2024-03-21_18-34-00.webm

notice the difference in ram usage behaviour after I delete the content of the config

Expected behavior
ram usage should not be so high?

Environment

  • NixOS 24.05.20240319.b06025f
  • Version of the code: nickel-lang-cli nickel 1.5.0 (rev 35a5246)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant