From owner-freebsd-stable@FreeBSD.ORG Fri Mar 27 00:22:46 2015 Return-Path: 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 B96FD312; Fri, 27 Mar 2015 00:22:46 +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 831BB1F3; Fri, 27 Mar 2015 00:22:46 +0000 (UTC) Received: from ultimatedns.net (localhost [127.0.0.1]) by udns.ultimatedns.net (8.14.9/8.14.9) with ESMTP id t2R0PMqt053074; Thu, 26 Mar 2015 17:25:28 -0700 (PDT) (envelope-from bsd-lists@bsdforge.com) To: J David , Kevin Oberman In-Reply-To: References: <20150316232404.GM2379@kib.kiev.ua> , From: "Chris H" Subject: Re: Significant memory leak in 9.3p10? Date: Thu, 26 Mar 2015 17:25:28 -0700 Content-Type: text/plain; charset=UTF-8; format=fixed MIME-Version: 1.0 Message-id: <1a80c0a3a7a587eef36118fd736203d9@ultimatedns.net> Content-Transfer-Encoding: 8bit Cc: freebsd-stable , "freebsd-questions@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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Mar 2015 00:22:46 -0000 On Thu, 26 Mar 2015 14:03:45 -0700 Kevin Oberman wrote > On Thu, Mar 26, 2015 at 12:46 PM, J David wrote: > > > On Mon, Mar 16, 2015 at 7:52 PM, J David wrote: > > > On Mon, Mar 16, 2015 at 7:24 PM, Konstantin Belousov > > > 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. > > > > These FreeBSD machines running out of swap space and dying continues > > to be a daily problem causing outages and unscheduled reboots. Is > > there really no way to even research what might be causing the > > problem? > > > > (Widening the cross-posting in the hopes of eliciting more help, so > > the brief summary of the problem orginally posted to freebsd-stable is > > that an unknown actor consumes all the user-space memory in the > > system, including swap space, to the point where processes are killed > > for being out of swap space, but if every process on the machine is > > stopped, very little of the user-space memory in use is freed. > > Original message with more details is here: > > https://lists.freebsd.org/pipermail/freebsd-stable/2015-March/081986.html > > .) > > > > There are no tmpfs mounts or md disks, so it would have to be one of > > the other causes. How can FreeBSD's use of persistent, anonymous > > shared memory objects be investigated, measured, or controlled so we > > can get a handle on this issue? > > > > This is just a shot in the dark and not a really likely one, but I have had > issues with Firefox leaking memory badly. I can free the space by killing > firefox and restarting it. > > It seems to be linked to certain web sites, probably javascript. I have not > been able to confirm which one does it. It just will start growing until > the system slows to a crawl as too many things are swapped out. Normally my > system does not touch swap. I can confirm this -- both regular, as well as ESR. Upgrading firefox [ultimately] has little-to-no effect. I have experienced this for near 2yrs. I suspect the [firefoxes] js engine. Any one of any number of sites could/would/will cause it. As Kevin already noted; stopping firefox, and starting it again, seems the only solution. > > If it is in user space, top should show it under RES. > -- > Kevin Oberman, Network Engineer, Retired > E-mail: rkoberman@gmail.com > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" --Chris