-
Notifications
You must be signed in to change notification settings - Fork 93
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
Inconsistent Segmentation Faults While lsp-zero is Enabled on MacOS #223
Comments
I'm using the same Mac version and experiencing similar issues (things used to work on my old Intel Mac). I'm not seeing any seg faults though, just no LSP support whatsover most of the time (it sometimes randomly works again?). Also no error logs in mason (or in nvim version:
checkhealth while the issue occurs:
Will investigate further by installing older versions of lsp-zero... |
I've further investigated this using a blank It seems the issue occurs only on very long Python scripts (>500 lines), and only when commenting in specific lines. I start to think this issue is on the pyright language server side. 🤔 @VonHeikemen Any tips how we could further debug this? Like e.g. how could I see the pyright logs? Sorry, I'm not very familiar with how things work internally. |
You can increase the level in the logs, add this in your config vim.lsp.set_log_level("debug") Then check the lsp logs again, using In neovim's wiki there is a section about debugging neovim itself. For more details you could join the neovim matrix channel, a lot of the developer core team are active there. |
Thanks! I can see the following logs when opening a file:
After that the language server just stops responding, and I can't interact with it anymore. E.g.
But there seems to be no response after that 🤔 |
Summary of Issue
When I launch Neovim while I have lsp-zero configured I regularly get a segmentation fault on startup
The above happens about 80% of the time when starting Neovim while lsp-zero is enabled. Commenting out the
lsp.setup()
call in my plugin configuration removes the problem. This only occurs on my MacOS setup and not my Linux setup though.When the above occurs it breaks stdout until the session is closed and restarted.
I've tried creating a core dump and inspecting with lldb but I was unable to find anything obvious on what went wrong in the stack trace so I would appreciate some help in trying to pinpoint exactly where the issue is occuring and if it's a larger bug or a misconfiguration of some kind.
I would appreciate any help or guidance.
System Details:
OS: MacOS Ventura 13.3.1
Shell: zsh
Neovim Version: 0.8.3 (compiled locally)
Terminal Emulator: iTerm2
Neovim Version
lsp-zero configuration
The text was updated successfully, but these errors were encountered: