Lennart Augustsson <lenn...@augustsson.net> writes: > I'm running the 32-bit Windows version of ghc-7.8.3. > > Here are two runs: > > $ RunMu +RTS -A64M -h -Sstat.log -i1 -RTS -c Strat.App.Abacus.Main > Compiling afresh Strat.App.Abacus.Main > Compiled afresh Strat.App.Abacus.Main, 1302.84s > > $ RunMu +RTS -A64M -Sstat.log -i1 -RTS -c Strat.App.Abacus.Main > Compiling afresh Strat.App.Abacus.Main > RunMu.exe: out of memory > > The binary is compiled without profiling, but in the first run I'm using > the -h flag to get the rudimentary heap profile. And with -h it works, but > without the flag it runs out of memory. > How does the produced profile look? How much memory do you expect this process to require? Can you get a backtrace of the crash? If you're lucky it will crash in RTS code, in which case the backtrace may be informative.
Cheers, - Ben
pgpOH1SghoKQU.pgp
Description: PGP signature
_______________________________________________ ghc-devs mailing list ghc-devs@haskell.org http://www.haskell.org/mailman/listinfo/ghc-devs
