-
Notifications
You must be signed in to change notification settings - Fork 213
Is it normal for hie to take ~4GB of memory per instance? #665
Comments
I believe this is caused by a memory leak in ghci, #580 and https://ghc.haskell.org/trac/ghc/ticket/15111 |
So should I read that as "Yes, but it shouldn't be"? If so, is this something that we generally just have to deal with for now or is there a known workaround? |
We have not been focusing on the memory footprint, more on functionality. So I have no idea of what savings can be made by optimising things. But I would prefer to do that once we know that GHC itself is not leaking as much. |
Understood. |
Having this issue, too, HIE is taking over 7GBs. |
Possibly duplicate of #412 |
If I'm understanding #580 correctly, memory leak issues should be fixed if you use GHC 8.6 or higher due to ghcMod's usage of |
Also there's this ugly workaround for now, https://dimjasevic.net/marko/2018/08/15/haskell-ide-the-memory-hog-engine/, thanks @codygman for the link. |
I currently have a workflow where I usually have a couple different projects open, each of them has the VSCode integration with hie. I find that each editor has it's own hie process and that process takes about 4G of RAM. Is this typical/expected or is something in my setup wrong/different than others?
The text was updated successfully, but these errors were encountered: