Internal error: unable to commit [ENOUGH] bytes of memory

[ghost]

General summary/comments (optional)

When running stack ghci
for the first time and it tries to install it I get Internal error: unable to commit [ENOUGH] bytes of memory where ENOUGH is approx. a gigabyte. My server has only 1G of ram.

BUT, after that, ghci runs fine and is indeed installed in .stack.

I could use a swap file or just upgrade my server but I thought it wasn’t normal for stack to consume such an amount of memory.

Steps to reproduce

On a DigitalOcean 1G droplet:

1. Install stack
2. stack ghci

Stack version

$ stack --version
Version 1.7.1, Git revision [...] x86_64 hpack-0.28.2

Method of installation

• curl https://get.haskellstack.org | sh

[ghost]

very wierd.
So if I understand you well. the installation does not end with a message that stack is installed somewhere.

[ghost]

No you’re right, unless run in verbose mode.

[ghost]

oke, we will investigate this.

[ghost]

I don’t know if it helps but it also happens when running ‘stack ghc’ or just ‘stack’ in a new project for the first time when no ghc is installed.

I encountered the very same error two months ago I believe and I’m pretty sure I solved it by temporarily upgrading my droplet with a few gb of memory.

[ghost]

Can you add a swap file to your enviroment and try again to install stack.

[ghost]

then it looks not a bug in stack but a problem with your digital ocean enviroment.

[ghost]

I’m testing with Fedora 28 right now. (I was using Debian 9.)

[ghost]

oke, hopefully with a swap file or more memory. I think that is more the problem then the distro.

[ghost]

So it is normal for stack to consume more than 1G of memory for running ? I mean, of course the issue is the memory here since I solved it the issue by adding more.

Update: yep, same error on Fedora with 1G of memory.

[ghost]

can it be that the memory is too little on the updating the Hackage index cache,
That is going to be fixed soon. Otherwise stack should not take that lot of memory

[ghost]

Can you paste a log where we can see where the memory is too little.

[ghost]

Here it is:
http://ix.io/1kbn

It seems related to Hackage’s index cache indeed.

[ghost]

oke, that problem is well known and being solved in one of the next versions.
Can I close this issue or do you have other questions

[ghost]

No it’s fine you can close it. Thanks.

[bsdshell]

when I try to use stack build for regex-tdfa, I have the same memory issue in my Ubuntu 1G vm.