Hacker News new | past | comments | ask | show | jobs | submit login

Your problem is the 2GB of swap. Get rid of it and it will just crash without 10min of slowdown (while swap disk is getting written to). </sarcasm>

Linux overcommitting memory and especially chrome/firefox beeing big-fat-memory-hogs are the problem. In fact every application which doesn't cope malloc beeing out of memory or assuming everybody has multiple gigs of memory to spare should "reevaluate".




Seriously though that’s a good idea. Might be better to just disable swap. :) Well, at least until I go out and buy more RAM.


The soft way would be to set ulimit for memory to something other than unlimited. To cap the max mem limit per process


Thanks, that’s a good suggestion.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: