On Tue, Aug 2, 2011 at 10:03 AM, per...@pluto.rain.com wrote:
C. P. Ghost cpgh...@cordula.ws wrote:
... when mplayer plays some (rare) video files.
Xorg then stays at 100% CPU, and it is impossible to kill it,
neither from the inside, nor from the outside (logged in via
ssh) with SIGKILL.
Yuri y...@rawbw.com writes:
I saw this with firefox, now I see the same with chrome.
After a while when the browser is launched with ~10 tabs open, Xorg
begins to consume 100% CPU and all graphics apps get
sluggish. Quitting the browser brings situation back to normal.
[...]
Have you tried
I saw this with firefox, now I see the same with chrome.
After a while when the browser is launched with ~10 tabs open, Xorg
begins to consume 100% CPU and all graphics apps get sluggish. Quitting
the browser brings situation back to normal.
It looks amazing to me that both firefox and
On Mon, Aug 1, 2011 at 8:56 AM, Yuri y...@rawbw.com wrote:
I saw this with firefox, now I see the same with chrome.
After a while when the browser is launched with ~10 tabs open, Xorg begins
to consume 100% CPU and all graphics apps get sluggish. Quitting the browser
brings situation back to
On Mon, 1 Aug 2011, C. P. Ghost wrote:
Running:
FreeBSD 8.2-STABLE #0 r222832 amd64
with
xorg-server-1.7.7_1,1
xorg-drivers-7.5.1
and the radeonhd driver:
radeonhd is defunct. Everything it does should be done better by the
radeon driver from xf86-video-ati.
C. P. Ghost cpgh...@cordula.ws wrote:
... when mplayer plays some (rare) video files.
Xorg then stays at 100% CPU, and it is impossible to kill it,
neither from the inside, nor from the outside (logged in via
ssh) with SIGKILL. Only a reboot helps here.
An unkillable process is almost
