From owner-freebsd-stable@FreeBSD.ORG  Mon Mar 16 23:52:11 2015
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 669852C2
 for <freebsd-stable@freebsd.org>; Mon, 16 Mar 2015 23:52:11 +0000 (UTC)
Received: from mail-ig0-x231.google.com (mail-ig0-x231.google.com
 [IPv6:2607:f8b0:4001:c05::231])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 2B9AABE9
 for <freebsd-stable@freebsd.org>; Mon, 16 Mar 2015 23:52:11 +0000 (UTC)
Received: by igbue6 with SMTP id ue6so58260775igb.1
 for <freebsd-stable@freebsd.org>; Mon, 16 Mar 2015 16:52:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:sender:in-reply-to:references:date:message-id:subject
 :from:to:cc:content-type;
 bh=B0ajGRYIGiSekWkomJ8TD4cBLmTLFsHKCKIi/bQugO8=;
 b=WJIP3S6HhLOK77eiWIuCinb/EQ5sV80LWdSK8+wgWfgxgIq4ih05NcRiaXYgv0C4wH
 rCZJaTHvspdDQDW3gMwg/PCZ1XAluHS9qnlKb5ngXoBp5N0WOshuwtExe1tqIDWx4map
 EB6Y8WQl0ZPEqb/nn7BoefJkShJVWgKehovM/FcWvlKudWt/TfeiU6GLQXAMlnj2T+Ou
 FD4sC1G4/p5cVst5Ja3WyawqaXgmkL2HtU3/aHT4SRnZX4vKg+vC5O/s2UaPNymxa/v2
 4TuXm6oI7IWLijGHiMQbc6pwSnqqALlhlcozdhFWddbtbmUaBFOcR5D0DHMPDAPTOCns
 U/PA==
MIME-Version: 1.0
X-Received: by 10.42.52.209 with SMTP id k17mr9320170icg.11.1426549930504;
 Mon, 16 Mar 2015 16:52:10 -0700 (PDT)
Sender: jdavidlists@gmail.com
Received: by 10.36.67.139 with HTTP; Mon, 16 Mar 2015 16:52:10 -0700 (PDT)
In-Reply-To: <20150316232404.GM2379@kib.kiev.ua>
References: <CABXB=RRhynY5FWvw3tHrLFRyitTemavXYLBpev5Mjs_kPqimXA@mail.gmail.com>
 <20150316232404.GM2379@kib.kiev.ua>
Date: Mon, 16 Mar 2015 19:52:10 -0400
X-Google-Sender-Auth: kxLvi8IdOi5Z7xxuOoPlx-UI3vU
Message-ID: <CABXB=RSt0MgEyoJs4o5utTg7oSu0RZ+-czeY0k-Ro+fRubK3kQ@mail.gmail.com>
Subject: Re: Significant memory leak in 9.3p10?
From: J David <j.david.lists@gmail.com>
To: Konstantin Belousov <kostikbel@gmail.com>
Content-Type: text/plain; charset=UTF-8
Cc: freebsd-stable <freebsd-stable@freebsd.org>
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Mar 2015 23:52:11 -0000

On Mon, Mar 16, 2015 at 7:24 PM, Konstantin Belousov
<kostikbel@gmail.com> wrote:
> There are a lot of possibilities to create persistent anonymous shared
> memory objects.  Not complete list is tmpfs mounts, swap-backed md disks,
> sysv shared memory, possibly posix shared memory (I do not remember which
> implementation is used in stable/9).

If that's the explanation, how could it be
detected/measured/investigated/resolved/prevented?

Under ordinary circumstances, machines will go run like this for days/weeks:

Mem: 549M Active, 3623M Inact, 567M Wired, 3484K Cache, 827M Buf, 3156M Free
Swap: 1024M Total, 1024M Free

Then, when this happens, it rapidly degrades from that to so bad that
processes start getting killed for being out of swap space.

Thanks!