From owner-freebsd-gecko@FreeBSD.ORG  Thu Sep  1 12:31:32 2011
Return-Path: <owner-freebsd-gecko@FreeBSD.ORG>
Delivered-To: gecko@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id ABFE21065670;
	Thu,  1 Sep 2011 12:31:32 +0000 (UTC) (envelope-from flo@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
	[IPv6:2001:4f8:fff6::28])
	by mx1.freebsd.org (Postfix) with ESMTP id 9AD228FC15;
	Thu,  1 Sep 2011 12:31:32 +0000 (UTC)
Received: from bender.solomo.local (localhost [127.0.0.1])
	by freefall.freebsd.org (8.14.4/8.14.4) with ESMTP id p81CVUAY084066;
	Thu, 1 Sep 2011 12:31:31 GMT (envelope-from flo@freebsd.org)
Message-ID: <4E5F7B22.40604@freebsd.org>
Date: Thu, 01 Sep 2011 14:31:30 +0200
From: Florian Smeets <flo@freebsd.org>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:6.0) Gecko/20110831 Thunderbird/6.0
MIME-Version: 1.0
To: Andriy Gapon <avg@freebsd.org>
References: <4E5F6753.3070402@FreeBSD.org> <4E5F737F.1070703@ksu.ru>
	<4E5F799C.7030509@FreeBSD.org>
In-Reply-To: <4E5F799C.7030509@FreeBSD.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gecko@freebsd.org
Subject: Re: firefox-6.0_1 spinning on a cpu
X-BeenThere: freebsd-gecko@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Gecko Rendering Engine issues <freebsd-gecko.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gecko>,
	<mailto:freebsd-gecko-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-gecko>
List-Post: <mailto:freebsd-gecko@freebsd.org>
List-Help: <mailto:freebsd-gecko-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-gecko>,
	<mailto:freebsd-gecko-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Sep 2011 12:31:32 -0000

On 01.09.2011 14:25, Andriy Gapon wrote:
> on 01/09/2011 14:58 Marat N.Afanasyev said the following:
>> I have a seamonkey with the same symptoms, from time to time it eats several cores
>> of my CPU.
>
> Just a general note: at these level of diagnosing it is not possible to say if you
> see the same problem or not.  That's why I tried to provide a little bit more
> detailed symptoms.
>

Yes, it's a known problem, however we did not get any further on this 
topic, yet.

We have a PR which was filed some time ago ports/156889 which describes 
a similar problem.

What i do know is that i can easily provoke it by going to 
http://localhost:$port where $port is some random port where nothing 
listens.

Adriy, I'm very happy that someone with kernel knowledge got interested 
in this ;)

Thanks,
Florian

P.S. I doubt it is fixed in 6.0.1