From owner-freebsd-questions@FreeBSD.ORG Tue Mar 3 16:02:24 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 A9A8C1065718 for ; Tue, 3 Mar 2009 16:02:24 +0000 (UTC) (envelope-from sneepre@mac.com) Received: from asmtpout030.mac.com (asmtpout030.mac.com [17.148.16.105]) by mx1.freebsd.org (Postfix) with ESMTP id 8FA5C8FC18 for ; Tue, 3 Mar 2009 16:02:24 +0000 (UTC) (envelope-from sneepre@mac.com) MIME-version: 1.0 Received: from [10.200.0.197] ([64.142.54.201]) by asmtp030.mac.com (Sun Java(tm) System Messaging Server 6.3-7.03 (built Aug 7 2008; 32bit)) with ESMTPSA id <0KFX001DSTV7B350@asmtp030.mac.com> for freebsd-questions@freebsd.org; Tue, 03 Mar 2009 08:02:10 -0800 (PST) Message-id: <9B2E2AAB-0866-4D91-9A4A-4E2D81A342E6@mac.com> From: Andrew Moran To: Mel In-reply-to: <200903030640.25554.fbsd.questions@rachie.is-a-geek.net> Date: Tue, 03 Mar 2009 08:01:54 -0800 References: <8806A36E-A839-481A-8E59-9F79DEB6B51A@me.com> <200903021439.55092.fbsd.questions@rachie.is-a-geek.net> <19C0CCFC-CBD5-4822-8838-4F10C4792C23@mac.com> <200903030640.25554.fbsd.questions@rachie.is-a-geek.net> X-Mailer: Apple Mail (2.930.3) Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7BIT X-Content-Filtered-By: Mailman/MimeDel 2.1.5 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 16:02:25 -0000 In Mar 3, 2009, at 7:40 AM, Mel wrote: > On Monday 02 March 2009 16:21:53 Andrew Moran wrote: > >>> 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. > > Could you show kenv kern.maxdsiz and if unset limits -H -d? Looks > like it's > 32G on my 6.x amd64, in which case setting it is a good idea. > echo 'kern.maxdsiz="8G"' >> /boot/loader.conf > echo 'kern.defdsiz="4G"' >> /boot/loader.conf Thank you for helping me. The earlier suggestion of toggling Perl Malloc didn't work, nor did syncing sources and installing new kernel and new world which is what I did lsat night. As for kernel settings, I don't have anything in my loader.conf, and I'm not entirely sure how to show things that aren't sysctls, as this one doesn't seem to be: celebrian# sysctl -a | grep kern.maxdsiz celebrian# sysctl -a | grep kern.defdsiz celebrian# (Btw, using Perl Malloc didn't work, nor did syncing sources and installing new kernel and new world.) I'm going to try your settings in loader.conf and see if they work for me. --Andy