SeaMonkey eats the CPU as of r232144
julian at freebsd.org
Sat Mar 3 06:16:50 UTC 2012
On 3/2/12 12:21 PM, deeptech71 at gmail.com wrote:
> Aleksandr Rybalko wrote:
>> On Fri, 2 Mar 2012 09:01:25 -0800
>> Adrian Chadd<adrian at 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 at freebsd.org mailing list
> To unsubscribe, send any mail to
> "freebsd-current-unsubscribe at freebsd.org"
More information about the freebsd-current