On 2006-11-12 13:14, Sven Jacobs wrote: >> All of this began about Nov 7, shortly after I did my most recent >> security upgrade (Oct 31), but I do not know if anything in that upgrade >> could be responsible.... >> > > I'm not quite sure when exactly this problem started but it definitively did > not occur in October. So here's a list of all packages I've installed or > upgraded in this month: > As I mentioned, everything was fine for about a week after my last upgrade. The only new or upgraded packages we have in common are:
kernel-default (clearly different versions of SuSe, however) qt3, which no Mozilla product uses mozilla-nss mozilla-nspr The last two were installed only after the problem arose, so cannot be the cause. That leaves the kernel, but I do not see how it could be responsible for just one package causing a problem. >> It is possible that something in one of the installed packages has >> caused Java and/or javascript to slow to a crawl. Java is a resource hog.... > My testing showed that no process takes up unusually much memory or cpu when > there's a "freeze". I also do not believe that the cause is Java or > JavaScript because the problem also occurs on sites which neither use one of > them. Are you sure there is no spike in Firefox's CPU usage? My system is an old, slow Pentium II running at 400 MHz, so would be far more sensitive to such a problem than a newer CPU. I ran "top" for a while to determine what Mozilla/Seamonkey normally required for CPU usage (20 to 24% for Seamonkey), and determined that at least quadrupled whenever things slowed down. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
