Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 01 Sep 2011 15:58:55 +0400
From:      "Marat N.Afanasyev" <amarat@ksu.ru>
To:        Andriy Gapon <avg@freebsd.org>
Cc:        gecko@freebsd.org
Subject:   Re: firefox-6.0_1 spinning on a cpu
Message-ID:  <4E5F737F.1070703@ksu.ru>
In-Reply-To: <4E5F6753.3070402@FreeBSD.org>
References:  <4E5F6753.3070402@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help

Andriy Gapon wrote:
>
> I observe the following problem - sometimes a firefox processes starts consuming a
> lot of CPU for no apparent reason.
> ktrace shows that it does the following:
>    9332 179912 firefox-bin 0.000007 CALL  poll(0x7fffff5fabc0,0x3,0x3e7fc18)
>    9332 179912 firefox-bin 0.000008 RET   poll 2
>    9332 179912 firefox-bin 0.000007 CALL  gettimeofday(0x7fffff5fadf0,0)
>    9332 179912 firefox-bin 0.000007 RET   gettimeofday 0
>    9332 179912 firefox-bin 0.000009 CALL  gettimeofday(0x7fffff5fadf0,0)
>    9332 179912 firefox-bin 0.000018 RET   gettimeofday 0
>    9332 179912 firefox-bin 0.000009 CALL
> getpeername(0x42,0x7fffff5faa90,0x7fffff5faa4c)
>    9332 179912 firefox-bin 0.000008 RET   getpeername -1 errno 57 Socket is not
> connected
>    9332 179912 firefox-bin 0.000008 CALL
> getpeername(0x43,0x7fffff5faa90,0x7fffff5faa4c)
>    9332 179912 firefox-bin 0.000008 RET   getpeername -1 errno 57 Socket is not
> connected
>    9332 179912 firefox-bin 0.000007 CALL  gettimeofday(0x7fffff5fab60,0)
>    9332 179912 firefox-bin 0.000008 RET   gettimeofday 0
>    9332 179912 firefox-bin 0.000018 CALL  poll(0x7fffff5fabc0,0x3,0x3e7fc18)
>    9332 179912 firefox-bin 0.000009 RET   poll 2
>    9332 179912 firefox-bin 0.000007 CALL  gettimeofday(0x7fffff5fadf0,0)
>    9332 179912 firefox-bin 0.000008 RET   gettimeofday 0
>    9332 179912 firefox-bin 0.000009 CALL  gettimeofday(0x7fffff5fadf0,0)
>    9332 179912 firefox-bin 0.000007 RET   gettimeofday 0
>    9332 179912 firefox-bin 0.000008 CALL
> getpeername(0x42,0x7fffff5faa90,0x7fffff5faa4c)
>    9332 179912 firefox-bin 0.000014 RET   getpeername -1 errno 57 Socket is not
> connected
>    9332 179912 firefox-bin 0.000008 CALL
> getpeername(0x43,0x7fffff5faa90,0x7fffff5faa4c)
>    9332 179912 firefox-bin 0.000007 RET   getpeername -1 errno 57 Socket is not
> connected
>    9332 179912 firefox-bin 0.000008 CALL  gettimeofday(0x7fffff5fab60,0)
>    9332 179912 firefox-bin 0.000007 RET   gettimeofday 0
>    9332 179912 firefox-bin 0.000007 CALL  poll(0x7fffff5fabc0,0x3,0x3e7fc18)
>
> and so on.
> The two sockets in question (66 and 67) appear as follows in sockstat output:
> avg      firefox-bi 9332  66 tcp4   92.249.64.71:44862    63.245.217.114:443
> avg      firefox-bi 9332  67 tcp4   92.249.64.71:34232    63.245.217.114:443
> Where:
> $ host 63.245.217.114
> 114.217.245.63.in-addr.arpa domain name pointer
> addons-versioncheck.zlb.phx.mozilla.net.
>
> So apparently this has something to do with automatic version check for addons.
>
> I am not sure if this is a general "cross-platform" bug or if it is specific to
> FreeBSD in some way.  E.g. maybe the error code is unexpected or what poll(2)
> returns is different from e.g. Linux.
>
> Maybe this is already fixed in 6.0.1?
>
> Anyone gets the same?  Anybody has an idea how to fix?
> Thank you!
I have a seamonkey with the same symptoms, from time to time it eats 
several cores of my CPU.

-- 
SY, Marat



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E5F737F.1070703>