From owner-freebsd-questions@FreeBSD.ORG Fri Mar 27 00:59:58 2015 Return-Path: Delivered-To: freebsd-questions@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 35781F84; Fri, 27 Mar 2015 00:59:58 +0000 (UTC) Received: from udns.ultimatedns.net (unknown [IPv6:2602:d1:b4d6:e600:4261:86ff:fef6:aa2a]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EAAA1786; Fri, 27 Mar 2015 00:59:57 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2R12YUM056338; Thu, 26 Mar 2015 18:02:40 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: J David In-Reply-To: References: <20150316232404.GM2379@kib.kiev.ua> <1a80c0a3a7a587eef36118fd736203d9@ultimatedns.net>, From: "Chris H" Subject: Re: Significant memory leak in 9.3p10? Date: Thu, 26 Mar 2015 18:02:40 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <8ff850e3a89d01436d3ab488a2f1f425@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: Kevin Oberman , freebsd-stable , "freebsd-questions@freebsd.org" X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2015 00:59:58 -0000 On Thu, 26 Mar 2015 20:28:15 -0400 J David wrote > On Thu, Mar 26, 2015 at 8:25 PM, Chris H wrote: > > As Kevin already noted; stopping firefox, and starting it again, > > seems the only solution. > > The machines in questions are servers, they do not run Firefox or any > GUI. And whatever is using the memory does not show up on ps or top. Fair enough. I'm still getting caught up, on the thread. Maybe another "shot in the dark". But speaking of Servers. We ran into trouble with a web server generating *enormous* error logs -- a runaway script. The result was, even tho there was far more than adequate space for the swelling log(s). Memory, and eventually Swap usage, began to climb quite steadily. Like I said; maybe a shot in the dark. But just thought I'd mention it. > > Thanks! --Chris --