undefined | Better HN

0 pointsben_bai5y ago0 comments

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".

0 comments

ymbeld5y ago

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.

ben_baiOP5y ago

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

ymbeld5y ago

Thanks, that’s a good suggestion.

j / k navigate · click thread line to collapse

0 pointsben_bai5y ago0 comments

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>

0 comments

ymbeld5y ago

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.

ben_baiOP5y ago

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

ymbeld5y ago

Thanks, that’s a good suggestion.

j / k navigate · click thread line to collapse