Cabal-2.2.0.1: out of memory (requested 1048576 bytes) on raspbian/rpi3 #5505
Comments
|
To be fair, this is rather a problem of GHC which is known to have some undesirable non-linear space-dimension complexities when big data structures are involved, and Cabal certainly makes good use of such large data structures. I expect that Cabal-2.4 pushed the envelope even a bit further than Cabal-2.2 did in terms of compile-time cost... so this is a trend that will keep going on. So I'm not sure what we can do here. :-/ PS: I notice you're using Stack; have you tried without Stack as well? |
|
Thank-you for your reply, @hvr. I suppose then I have a few questions:
If it is of any assistance to someone willing to investigate this, I'm happy to donate access to one of the Scaleway ARMv7 servers. |
with a recent to the |
|
There seems to be a (resolved) ticket for this here though I can't figure out how it was actually resolved. I ran into this in basically the same context. |
|
Are you also on openbsd? if so the answer seems to be to change values in |
|
I am now getting out of memory when I compile Cabal-2.4.1.0 on a Linux machine using ghc-8.2.2. I have deliberately set ulimit -v to 2GB address space (half of the physical memory on this machine) because otherwise some (usually Haskell) programs cause my machine to practically freeze so I am no longer able to manually kill them and have to use a hard reset. Building Cabal-2.2.x works fine in this setting. |
|
This seems to be a GHC rather than Cabal issue. Does something like setting the |
|
@m-renaud I believe that is a separate issue? I'm not getting panics on my banana pi. |
|
@23Skidoo when I try it fails with ...which may be a separate GHC bug, perhaps? |
|
I'd use |
|
Same error with |
|
I think we should probably close this. Nothing to really be done vis a vis cabal. |
I'm working on a project that runs on a Raspberry Pi. As part of the build pipeline it creates a Docker image with a load of packages already installed in order to speed up deployments. One of these packages is
Cabal-2.2.0.1.When I attempt to compile
Cabal-2.2.0.1, it churns away for several hours before eventualling reportingghc: out of memory (requested 1048576 bytes).Cabal-1.24.2.0does not suffer from this problem, building in a reasonable amount of time given the device's specifications.Reproduction Steps
These are specific to compiling on a
rpi3runningraspbianbut I was also able to produce the same result when compiling on one of Scaleway's ARMv7 servers.ghc-8.2.2(conveniently there is a pre-built binary that works onrpi3)Cabal-2.2.0.1Note that the logs below show the commands I'm running in the Dockerfile, if that's easier to follow.
System Information
Logs
The text was updated successfully, but these errors were encountered: