Date: Sat, 03 Mar 2012 09:40:54 +0100 From: deeptech71@gmail.com To: freebsd-current@freebsd.org Subject: Re: SeaMonkey eats the CPU as of r232144 Message-ID: <4F51D916.5090301@gmail.com> In-Reply-To: <4F51693C.1020403@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> <4F51693C.1020403@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
David Xu wrote: > I am also running the seamonkey and can not reproduce the problem. > maybe he did hit the race window when I was committing the patches ? > can he update and install the world and kernel again to see if the problem > is still existing ? Yes, he has just rebuilt his world and kernel again, using the latest revision, and he found that the problem disappeared. Although SeaMonkey's CPU usage still doesn't snap to 0 during inactivity. David Xu wrote: > I suspect that your kernel and libthr are out of sync. You have > installed only new version of kernel > or libthr and forgotten to install another ? With -CURRENT, it is better > to update whole tree and > install whole tree includes kernel. No, I deliberately didn't build a new world (because it takes ~10 times as long to build a world+kernel combination compared to just a kernel). I always had the impression that using an older world with a more recent kernel is almost always supported, and the exceptional cases are noted in the UPDATING file, as a quote shows: "User utilities using SIOCAIFADDR, SIOCAIFADDR_IN6, e.g. ifconfig(8), need to be recompiled.".
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F51D916.5090301>