From owner-freebsd-ports@FreeBSD.ORG Wed Dec 29 10:10:17 2010 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EA767106566B for ; Wed, 29 Dec 2010 10:10:17 +0000 (UTC) (envelope-from freebsd-ports@herveybayaustralia.com.au) Received: from mail.unitedinsong.com.au (mail.unitedinsong.com.au [150.101.178.33]) by mx1.freebsd.org (Postfix) with ESMTP id 9E8058FC0C for ; Wed, 29 Dec 2010 10:10:17 +0000 (UTC) Received: from laptop1.herveybayaustralia.com.au (laptop1.herveybayaustralia.com.au [192.168.0.193]) by mail.unitedinsong.com.au (Postfix) with ESMTP id 253ED5C21 for ; Wed, 29 Dec 2010 19:58:32 +1000 (EST) Message-ID: <4D1B044F.6050903@herveybayaustralia.com.au> Date: Wed, 29 Dec 2010 19:50:07 +1000 From: Da Rock User-Agent: Mozilla/5.0 (X11; U; FreeBSD amd64; en-US; rv:1.9.1.16) Gecko/20101227 Thunderbird/3.0.11 ThunderBrowse/3.3.4 MIME-Version: 1.0 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: libxul build hit the roof! X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2010 10:10:18 -0000 I was doing an update of my system, and I hit these errors and skipped builds all over the place; so I've been eliminating them one by one and making the skipped list smaller. In the process of these investigations I noticed that my system practically froze several times and I spotted multiple pfaults through top. I also ran a lone run of just libxul as it was one in the list with an error: new compiler error. I then basically shut every app I was running down and ran it again with just top showing. I found that at least one part hit the roof of my system, with nsCharacter... something or rather running at 1430M+ in swap, and 520M+ resident when compiling. Does anyone else think it might be wise to put a warning during build saying that this could take over 2G+ of memory to compile, and rebuild with no apps running if it fails?