WSL: Running out of memory on `stack setup`
Please use the following bug reporting template to help produce actionable and reproducible issues. Please try to ensure that the reproduction is minimal so that the team can go through more bugs!
-
A brief description I installed ghc and stack on build 14986 and attempted to run
stack setup. -
Expected results This should setup and install the latest version of ghc globally.
-
Actual results (with terminal output if applicable)
stack setupruns out of memory when making ghc. However, only 4 GBs of RAM are being used when I have 8. The output from stack:
strip: createProcess: fork: resource exhausted (Cannot allocate memory)
make[1]: *** [install_packages] Error 1
make: *** [install] Error 2
Error encountered while installing GHC with
make install
run in /home/kitfreddura/.stack/programs/x86_64-linux/ghc-8.0.1.temp/ghc-8.0.1/
-
Your Windows build number 14986
-
Steps / All commands required to reproduce the error from a brand new installation
sudo apt-get install ghc
curl -sSL https://get.haskellstack.org/ | sh
stack setup
- Required packages and commands to install ghc, stack
About this issue
- Original URL
- State: closed
- Created 10 years ago
- Reactions: 2
- Comments: 17 (7 by maintainers)
Ok, I have confirmed that I was successfully able to run “stack setup” on a build that has my memory fix. How long does that operation typically take on native Ubuntu? It took quite a long time (over an hour) but that could be because I was using a debug driver which has a lot of extra checks and validation.
Once I’ve configured the Haskell tool stack do you have a pointer to some unit tests or other commands I can run to validate everything is functional?
The memory usage reporting is unrelated. That’s related to procfs files not containing actual memory usage info. That issue is being fixed right now.
@fpqc - Good question, I honestly don’t know.
@alandao - The performance issue is being tracked by #1671 - @stehufntdev is working on a fix.