From owner-freebsd-questions@FreeBSD.ORG Tue Mar 3 02:21:54 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 6CB031065726 for ; Tue, 3 Mar 2009 02:21:54 +0000 (UTC) (envelope-from sneepre@mac.com) Received: from asmtpout017.mac.com (asmtpout017.mac.com [17.148.16.92]) by mx1.freebsd.org (Postfix) with ESMTP id 57B068FC1B for ; Tue, 3 Mar 2009 02:21:54 +0000 (UTC) (envelope-from sneepre@mac.com) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Received: from cenarius.apple.com ([17.228.13.75]) by asmtp017.mac.com (Sun Java(tm) System Messaging Server 6.3-7.03 (built Aug 7 2008; 32bit)) with ESMTPSA id <0KFW0069EP4HHW40@asmtp017.mac.com> for freebsd-questions@freebsd.org; Mon, 02 Mar 2009 17:21:53 -0800 (PST) Message-id: <19C0CCFC-CBD5-4822-8838-4F10C4792C23@mac.com> From: Andrew Moran To: Mel In-reply-to: <200903021439.55092.fbsd.questions@rachie.is-a-geek.net> Date: Mon, 02 Mar 2009 17:21:53 -0800 References: <8806A36E-A839-481A-8E59-9F79DEB6B51A@me.com> <200903021439.55092.fbsd.questions@rachie.is-a-geek.net> X-Mailer: Apple Mail (2.930.3) Cc: freebsd-questions@freebsd.org Subject: Re: SpamAssassin/Perl eating enormous amounts of memory? 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: Tue, 03 Mar 2009 02:21:54 -0000 On Mar 2, 2009, at 3:39 PM, Mel wrote: > > This is hard to debug, but I'd first toggle the PERL_MALLOC option > in the > configuration dialog for the perl port. If this doesn't solve the > problem, > then you'd have to get a ktrace to get some indication of what is > allocating > the memory. > Thank you for your suggestion. I'll try compiling Perl and it's dependencies without using PERL_MALLOC. > What's even weirder is that the process gets that far. Did you play > with > kern.maxdsiz loader tuneable? > If so, set it lower, so you can at least have the machine in a > usable state at > all times. 4G should be enough for any process and should give > enough time > for you to spot the leak and get a ktrace. > Nope, I haven't tweaked any kernel settings, just using the generic DEFAULT amd64 kernel. I've been way about tweaking settings because I don't fully understand what the 'correct' values for my setup are.