From owner-freebsd-current@FreeBSD.ORG Fri Mar 2 20:16:51 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 929FB106566C for ; Fri, 2 Mar 2012 20:16:51 +0000 (UTC) (envelope-from deeptech71@gmail.com) Received: from mail-ee0-f54.google.com (mail-ee0-f54.google.com [74.125.83.54]) by mx1.freebsd.org (Postfix) with ESMTP id 176228FC12 for ; Fri, 2 Mar 2012 20:16:50 +0000 (UTC) Received: by eekd17 with SMTP id d17so773572eek.13 for ; Fri, 02 Mar 2012 12:16:50 -0800 (PST) Received-SPF: pass (google.com: domain of deeptech71@gmail.com designates 10.213.31.209 as permitted sender) client-ip=10.213.31.209; Authentication-Results: mr.google.com; spf=pass (google.com: domain of deeptech71@gmail.com designates 10.213.31.209 as permitted sender) smtp.mail=deeptech71@gmail.com; dkim=pass header.i=deeptech71@gmail.com Received: from mr.google.com ([10.213.31.209]) by 10.213.31.209 with SMTP id z17mr42367ebc.220.1330719410209 (num_hops = 1); Fri, 02 Mar 2012 12:16:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=Zm9fKhAG9IEh79SDhZhEYJxlLsR/ayN5Q/Sa1GH8hIA=; b=JLekVHNX6/v3KJx1+HAYq2lWRGhyVeQ8OnW0mtUh3KSo92IXlBmay4xI9pXrOkXGyq XMp8VYhVmM7kZyOJ09nxpkuv85WSJmDEK4aKFmevVp/9+t+TOSmBaJ4zXVbmaUXOq6rm CXOtxq+aRWXpjySzuHCmRYCXBUSj29MYOxPBGnErFIXrc29fOtz38D1GP6UtQ/VJNzY8 g+BKeTdFtas96egu25zDsfxOp7I2Bu6vs8VAgiU7ljuZowqH0mYKSj3BRjy6kxZDSUKN LUBCrlPax5duJv8bUKAcVoKycoPPlx/vViLACZos2yUOFD65uW2F/y9zCB7TClnmrsve l8Ww== Received: by 10.213.31.209 with SMTP id z17mr34857ebc.220.1330719410134; Fri, 02 Mar 2012 12:16:50 -0800 (PST) Received: from [192.168.1.80] (dsl4E5C32D7.pool.t-online.hu. [78.92.50.215]) by mx.google.com with ESMTPS id n17sm24274740eei.3.2012.03.02.12.16.48 (version=SSLv3 cipher=OTHER); Fri, 02 Mar 2012 12:16:49 -0800 (PST) Message-ID: <4F512BB0.9070202@gmail.com> Date: Fri, 02 Mar 2012 21:21:04 +0100 From: deeptech71@gmail.com User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:10.0.2) Gecko/20120229 Firefox/10.0.2 SeaMonkey/2.7.2 MIME-Version: 1.0 To: freebsd-current@freebsd.org References: <4F50CE89.6010009@gmail.com> <20120302210810.c67d3030.ray@ddteam.net> In-Reply-To: <20120302210810.c67d3030.ray@ddteam.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: SeaMonkey eats the CPU as of r232144 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Mar 2012 20:16:51 -0000 Aleksandr Rybalko wrote: > On Fri, 2 Mar 2012 09:01:25 -0800 > Adrian Chadd wrote: > >> Ok. So it's that exact commit? >> >> david, what did you break? :) >> > > I bet it is old enough :) > I'm on 9.0-PRERELEASE #3 r227950 and when Seamonkey can't reach some > document it get 100% cpu. one time I even attach to it and found what > seamonkey polling socket very-very fast, but no I'm have not so much > free time to found what really broken. IIRC same happen in FF also. No, this 100% CPU usage began a few days ago, with r232144. Although generally, the property that SeaMonkey's CPU usage slowly converges (instead of snapping) to 0 is WRONG, and that can be confirmed by the fact that on FreeBSD 9.0-RELEASE (as reported by someone) and Windows XP, SeaMonkey's CPU usage is snappy.