Is it normal that a user can take down the whole system by using too much memory?
galtsev at kicp.uchicago.edu
Sun Jun 3 02:50:39 UTC 2018
On Sat, June 2, 2018 6:46 pm, RW via freebsd-questions wrote:
> On Sat, 02 Jun 2018 19:25:31 -0400
> Brennan Vincent wrote:
>> I'm also curious, however, to learn more from an OS design
>> perspective. Why isn't it possible for the kernel to realize it
>> should kill `eatmem` rather than make the system unusable?
> I did something similar a few years ago, and the process was reliably
Indeed you sound like saying, no, regular user putting the system on the
knees by just grabbing all memory is not normal. And I would second that.
I didn't do such test to FreeBSD (how thoughtless of me), but in the past
when I was mostly Linux guy, I did that to Linux systems routinely. RedHat
(and clones) as well as unpatched by anybody latest Linux kernel built
with all default configuration were always consistently invoking OOM (Out
Of Memory) killer, which consistently was killing the offender, even in
presence of other processes possessing large junks of memory. Once I tried
SUSE (ver 7), and its stock kernel was crashed by this little memory leak
program I used for tests. I gave up on SUSE once and forever then.
So, killing the offender is a must IMHO. However, on some systems before
the offender gets killed the system may be on its knees for some time, and
for how long mostly will depend on how sysadmin set it up. Say, if there
is very large swap space, then until it is exhausted, the situation is not
considered critical to kill some process. And the machine that is using
swap a lot will effectively be thousands of times slower.
> freebsd-questions at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
Sr System Administrator
Department of Astronomy and Astrophysics
Kavli Institute for Cosmological Physics
University of Chicago
More information about the freebsd-questions