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

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

Open
CaptJakk opened this Issue Jun 28, 2018 · 8 comments

Comments

Projects
None yet
6 participants
@CaptJakk
Copy link

CaptJakk commented Jun 28, 2018

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?

@bubba

This comment has been minimized.

Copy link
Collaborator

bubba 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

@CaptJakk

This comment has been minimized.

Copy link
Author

CaptJakk 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

This comment has been minimized.

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.

@CaptJakk

This comment has been minimized.

Copy link
Author

CaptJakk commented Jul 6, 2018

Understood.

@JasonMFry

This comment has been minimized.

Copy link
Contributor

JasonMFry commented Jul 11, 2018

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

@kfigiela

This comment has been minimized.

Copy link

kfigiela commented Aug 17, 2018

Possibly duplicate of #412

@codygman

This comment has been minimized.

Copy link

codygman commented Nov 21, 2018

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.

@JasonMFry

This comment has been minimized.

Copy link
Contributor

JasonMFry commented Nov 21, 2018

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 join this conversation on GitHub. Already have an account? Sign in to comment