Open gfarrell opened 3 days ago
Hi, thank you for the bug report!
Can you reproduce the issue? Can you link the project the issue is reproducible on?
Otherwise, can you provide the full logs of the run? If possible, pass --debug
to HLS to get even more logs.
At the moment, we are not aware of a memory leak in HLS and the size of your project is indeed tiny.
Hi @fendor:
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: