Date: Sun, 04 Sep 2011 20:19:56 +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: <4E63A52C.7010100@ksu.ru> In-Reply-To: <4E5F799C.7030509@FreeBSD.org> References: <4E5F6753.3070402@FreeBSD.org> <4E5F737F.1070703@ksu.ru> <4E5F799C.7030509@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > 28511 seamonkey-bin CALL getpeername(0x66,0x7fffff5fba70,0x7fffff5fba34) 28511 seamonkey-bin RET getpeername -1 errno 57 Socket is not connected 28511 seamonkey-bin CALL getpeername(0x6b,0x7fffff5fba70,0x7fffff5fba34) 28511 seamonkey-bin RET getpeername -1 errno 57 Socket is not connected 28511 seamonkey-bin CALL getpeername(0x64,0x7fffff5fba70,0x7fffff5fba34) 28511 seamonkey-bin RET getpeername -1 errno 57 Socket is not connected corresponding sockets: marat seamonkey- 28511 100 tcp4 127.0.0.1:53964 127.0.0.1:443 marat seamonkey- 28511 102 tcp4 127.0.0.1:49377 127.0.0.1:443 marat seamonkey- 28511 108 tcp4 127.0.0.1:18546 127.0.0.1:443 I didn't try your patch yet, waiting for 2.3.2 in ports ;) -- SY, Marat
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E63A52C.7010100>