Date: Fri, 02 Mar 2012 22:16:54 -0800 From: Julian Elischer <julian@freebsd.org> To: deeptech71@gmail.com Cc: freebsd-current@freebsd.org Subject: Re: SeaMonkey eats the CPU as of r232144 Message-ID: <4F51B756.20807@freebsd.org> In-Reply-To: <4F512BB0.9070202@gmail.com> References: <CAF6hryQxh6df9ZoyGk8ebHbvrXcZDhihju7_miVEnavbY9km4A@mail.gmail.com> <CAJ-Vmon%2Bi=BBf8EW-PQWAxuH6EstdW1HdVp8dF7uOJSFJXLs0A@mail.gmail.com> <4F50CE89.6010009@gmail.com> <CAJ-Vmom56agc-vs%2BpADAn6yr6qTy7Yi%2BQS49%2Bn8YemHDbcjf3Q@mail.gmail.com> <20120302210810.c67d3030.ray@ddteam.net> <4F512BB0.9070202@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 3/2/12 12:21 PM, deeptech71@gmail.com wrote: > Aleksandr Rybalko wrote: >> On Fri, 2 Mar 2012 09:01:25 -0800 >> Adrian Chadd<adrian@freebsd.org> 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. maybe related to the over-enthusiastic timeouts we've been seeing on 9.0 and pthread condvar_timedwait() > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F51B756.20807>