Skip to content
This repository has been archived by the owner on Oct 7, 2020. It is now read-only.

Is it normal for hie to take ~4GB of memory per instance? #665

Open
ProofOfKeags opened this issue Jun 28, 2018 · 8 comments
Open

Is it normal for hie to take ~4GB of memory per instance? #665

ProofOfKeags opened this issue Jun 28, 2018 · 8 comments

Comments

@ProofOfKeags
Copy 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?

@lukel97
Copy link
Collaborator

lukel97 commented Jun 29, 2018

I believe this is caused by a memory leak in ghci, #580 and https://ghc.haskell.org/trac/ghc/ticket/15111

@ProofOfKeags
Copy link
Author

ProofOfKeags commented Jun 29, 2018

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?

@alanz
Copy link
Collaborator

alanz commented Jul 5, 2018

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.

@ProofOfKeags
Copy link
Author

Understood.

@tillydray
Copy link
Contributor

Having this issue, too, HIE is taking over 7GBs.

@kfigiela
Copy link

Possibly duplicate of #412

@codygman
Copy link

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 loadInterface taking advantage of dontLeakTheHPT.

@tillydray
Copy link
Contributor

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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants