From owner-freebsd-hackers@freebsd.org  Fri Apr 20 18:09:24 2018
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 79BCEF8B26E
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Fri, 20 Apr 2018 18:09:24 +0000 (UTC) (envelope-from yuri@rawbw.com)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
 by mx1.freebsd.org (Postfix) with ESMTP id F2F8C74C10
 for <freebsd-hackers@FreeBSD.org>; Fri, 20 Apr 2018 18:09:23 +0000 (UTC)
 (envelope-from yuri@rawbw.com)
Received: from yv.noip.me (c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132])
 (authenticated bits=0)
 by shell1.rawbw.com (8.15.1/8.15.1) with ESMTPSA id w3KHwCA1033549
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO)
 for <freebsd-hackers@FreeBSD.org>; Fri, 20 Apr 2018 10:58:13 -0700 (PDT)
 (envelope-from yuri@rawbw.com)
X-Authentication-Warning: shell1.rawbw.com: Host
 c-24-4-131-132.hsd1.ca.comcast.net [24.4.131.132] claimed to be yv.noip.me
To: Freebsd hackers list <freebsd-hackers@FreeBSD.org>
From: Yuri <yuri@rawbw.com>
Subject: Runaway processes freeze the system
Message-ID: <e6655853-07e6-4473-31c6-b35f35990ec5@rawbw.com>
Date: Fri, 20 Apr 2018 10:58:11 -0700
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101
 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Apr 2018 18:09:24 -0000

I am getting this problem again and again: when some process allocates 
too much memory the system to freezes.

My memory size is 24GB, and swap is only 4GB. I know that increasing the 
swap size should reduce the chance of this happening, but it obviously 
can't eliminate the problem.


What is the expected behavior of the system in such situation? To me it 
looks like it is wait-and-see, and this causes this problem.

A better strategy would be to maybe wait for some time, but if when the 
problem persists to kill the largest, the most active, or the offending 
process.


11.1 amd64


Yuri