You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems quite common that when GHC stops with SIGKILL (exit code -9), it's because the process was killed by an OOM killer. It would be nice if Cabal could print a helpful message describing that GHC was killed by a signal, and that it's likely to be because of a lack of memory.
The text was updated successfully, but these errors were encountered:
It seems quite common that when GHC stops with SIGKILL (exit code -9), it's because the process was killed by an OOM killer. It would be nice if Cabal could print a helpful message describing that GHC was killed by a signal, and that it's likely to be because of a lack of memory.
The text was updated successfully, but these errors were encountered: