On Wednesday 25 April 2012 05:15:12 Jonathan Nieder wrote: > David Baron wrote: > >> How do you > >> know that it is chromium that is misbehaving?) > > > > As I said, it might not be. > > That doesn't answer the question at all. :) > > In "top" does chromium show up as a process consuming more memory or CPU > than others? If not, which process does? What prompted you to file this > bug against chromium --- does it happen more often while web browsing > than during idle times and other work, for example?
Yes, it does. It will, for whatever reason, not show in a yakuake session, but if I escape out to a "real" terminal session, there is a chromium, nice=0 eating 100% CPU. Manually run sessions are niced to 15. The nice=0 is that "service" (though I thought I placed nice on its command line and later disabled it entirely but it was reenabled). This is why the bug was filed against Chromium. The problem occurs after a few minutes live, regardless of usage. I have not seen a similarly symptomed kwin / nvidia problem that has gotten complaints on the mailing lists. I have had 100% problems without Chromium (but that service might have been around anyway). -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
