On 04/16/2013 12:42 PM, Neil Van Dyke wrote:
On these out-of-memory conditions, you might want to look at the kernel
logs for what the OOM-killer said about what processes were running,
their sizes, and who it thought the culprit was.

It was *definitely* Racket: I was watching htop at the time.

 Racket Developers list:

Reply via email to