-
-
Notifications
You must be signed in to change notification settings - Fork 369
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
Possible memory leak (HLS got OOM-killed after being idle for a while) #4456
Comments
Hi, thank you for the bug report! At the moment, we are not aware of a memory leak in HLS and the size of your project is indeed tiny. |
Hi @fendor:
|
May I know how to get log when I´m using Neovim+Haskell.vim+ Haskell LSP ? |
I just do |
@gfarrell Thanks for the logs, but I am afraid they don't contain much information. Can you run your HLS executable with the |
Your environment
hie.yaml
file)? No, only set the formatting programmes via lspconfigSteps to reproduce
I had been working in a project, left my laptop suspended for a few days, reopened it, was doing something else (in a web browser), hadn't opened the project, then the system froze and the OOM killer killed HLS.
Expected behaviour
I would not expect HLS memory requirements to keep growing -- this is not an enormous project (see cloc stats below). There are five components (library, executable, three tests suites, and a debug executable).
Actual behaviour
HLS stats just seem totally off (orders of magnitude greater than every other task).
Debug information
The only logs I have from today for HLS are the following:
The text was updated successfully, but these errors were encountered: