mathworks / mathworks/MATLAB-language-server

High memory usage in Nvim with mason, mason-lspconfig, nvim-lspconfig

Open
#48 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
TypeScript
Stars
125
Forks
21
PR merge metrics
No merged PRs in 30d

Description

Describe the bug
When I open any buffer that is a Matlab file, the LSP server starts and has ~2GB of memory on each tmux window. Since I use many windows for different repos simultaneously in one tmux session, my RAM tends to overflow if I am not careful.
Also the language server process does not end when I just close the terminal containing the tmux session. If I close the windows individually, the corresponding processes also stop.

To Reproduce
Steps to reproduce the behavior:

  1. Start tmux
  2. Open nvim and edit a matlab file
  3. Open a new window Ctrl-b + c, go to that window, repeat 1.+2.
  4. Open btop or top and filter for matlab process.

Expected behavior
I would expect the LSP to be more lightweight and not use up so much RAM?! According to the screenshot, an entire MATLAB instance is started to run the language server?!

Screenshots

btop screenshot

Useful Information

  • OS Version: Ubuntu 20.04 with nvim v0.10.1
  • Language Server Client: matlab_ls in combination with mason, mason-lspconfig and nvim-lspconfig
  • Client Version: commit hash eb1aab2e85dcf461e070b3d34e85aff15fcb9ada
  • Node version: v18.0.0
  • (relevant) Lazy Nvim LSP config:
return {
    {
        'williamboman/mason.nvim',
        config = function()
            require('mason').setup({})
        end
    },
    {
        'williamboman/mason-lspconfig.nvim', -- bridges Mason with nvim-lspconfig
        config = function()
            require('mason-lspconfig').setup({
                ensure_installed = {
                    'matlab_ls',
                    'bashls',
                    'lua_ls',
                    'clangd',
                    'ltex',
                    'marksman',
                    'gitlab_ci_ls',
                    'yamlls',
                },
            })
        end
    },
    {
        'neovim/nvim-lspconfig',
        dependencies = { 'hrsh7th/cmp-nvim-lsp'},
        config = function()
            local lspconfig = require('lspconfig')
            local capabilities = require('cmp_nvim_lsp').default_capabilities()
            lspconfig.matlab_ls.setup({
                capabilities = capabilities,
                filetypes = { "matlab" },
                settings = {
                    matlab = {
                        installPath = "/home/sh/programs/MATLAB/R2023a/", -- also tried not setting this
                        telemetry = false, 
                    },
                },
                single_file_support = true, -- also tried false 
            })
            lspconfig.bashls.setup({
                capabilities = capabilities,
                filetypes = { "sh", "zsh", "bash" },
                settings = {
                    bashls = {
                        lint = {
                            enable = true,
                            diagnostics = true,
                            use = { "shellcheck" },
                        },
                    },
                },
            })
            lspconfig.lua_ls.setup({
                capabilities = capabilities,
                settings = {
                    Lua = {
                        diagnostics = {
                            globals = { 'vim' } -- avoids warnings that vim is not found
                        }
                    }
                }
            })
            local function quickfix() vim.lsp.buf.code_action({ apply = true }) end
            local map = require('utils').map
            vim.api.nvim_create_autocmd('LspAttach', {
                callback = function(args)
                    -- mappings
                end
            })
        end
    },
}

Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the report with the provided Neovim, tmux, Ubuntu, and MATLAB configuration, then inspect how matlab_ls is launched and stopped. Confirm whether each tmux window creates a separate MATLAB process and whether closing the terminal leaves it running. Done means memory usage and process cleanup match the expected behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
neovim, typescript
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.