From owner-freebsd-questions@FreeBSD.ORG Mon Feb 13 21:54:16 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 4C90E16A422 for ; Mon, 13 Feb 2006 21:54:16 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id B7CCC43D48 for ; Mon, 13 Feb 2006 21:54:15 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id C904A5CB5; Mon, 13 Feb 2006 16:54:14 -0500 (EST) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 29917-09; Mon, 13 Feb 2006 16:54:14 -0500 (EST) Received: from [199.103.21.238] (pan.codefab.com [199.103.21.238]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by pi.codefab.com (Postfix) with ESMTP id 133B35C73; Mon, 13 Feb 2006 16:54:14 -0500 (EST) In-Reply-To: <20060213214053.GA20537@panix.com> References: <1139792505.30118.254198744@webmail.messagingengine.com> <43F0434F.2000703@locolomo.org> <1139826617.10634.254226042@webmail.messagingengine.com> <20060213214053.GA20537@panix.com> Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <010CAD73-FAA5-4468-B35A-6E526FF0CFDD@mac.com> Content-Transfer-Encoding: 7bit From: Charles Swiger Date: Mon, 13 Feb 2006 16:54:13 -0500 To: David Scheidt X-Mailer: Apple Mail (2.746.2) X-Virus-Scanned: amavisd-new at codefab.com Cc: Robert Leftwich , 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:54:16 -0000 On Feb 13, 2006, at 4:40 PM, David Scheidt wrote: >> 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. For contrast, I've got a Python-based daemon which handles 100K to 1 million logfile lines a day and spits them into a processing/ reporting system using either XMLRPC or SOAP, and it stays up for months without leaking memory or changing in size. As I said earlier, "top -o size" will identify the process(es) which is/are using excessive memory. -- -Chuck