From owner-freebsd-questions@FreeBSD.ORG Mon Feb 13 21:40:56 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0B3D316A420 for ; Mon, 13 Feb 2006 21:40:56 +0000 (GMT) (envelope-from dscheidt@panix.com) Received: from mail3.panix.com (mail3.panix.com [166.84.1.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id B353C43D45 for ; Mon, 13 Feb 2006 21:40:54 +0000 (GMT) (envelope-from dscheidt@panix.com) Received: from panix2.panix.com (panix2.panix.com [166.84.1.2]) by mail3.panix.com (Postfix) with ESMTP id B1B1013A9A1; Mon, 13 Feb 2006 16:40:53 -0500 (EST) Received: (from dscheidt@localhost) by panix2.panix.com (8.11.6p3/8.8.8/PanixN1.1) id k1DLesA16138; Mon, 13 Feb 2006 16:40:54 -0500 (EST) Date: Mon, 13 Feb 2006 16:40:54 -0500 From: David Scheidt To: Robert Leftwich Message-ID: <20060213214053.GA20537@panix.com> References: <1139792505.30118.254198744@webmail.messagingengine.com> <43F0434F.2000703@locolomo.org> <1139826617.10634.254226042@webmail.messagingengine.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1139826617.10634.254226042@webmail.messagingengine.com> User-Agent: Mutt/1.5.10i Cc: freebsd-questions@freebsd.org Subject: Re: Memory leak? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2006 21:40:56 -0000 On Mon, Feb 13, 2006 at 09:30:17PM +1100, Robert Leftwich wrote: > From: Robert Leftwich > > On Mon, 13 Feb 2006 09:29:03 +0100, "Erik Norgaard" > said: > > > > Do you run other applications also? > > > > There was a discussion on CURRENT@ some weeks ago about a memory leak > > that turned out to be firefox with some extensions, updates are > > available now. > > > > Unfortunately no, its cli only, no x, pretty much just Postgres and > Python and C :-( I've seen (very, very, very, very) large memory leaks on long-lived Python processes. I haven't looked at it to figure out if it's python, some module, or the application doing something stupid. But the processes will grow until they hit their limits.