From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4
Description of problem:
When loading https://www.redhat.com/archives/fedora-devel-list/2005-June/msg00849.html, X freezes. No keyboard input accepted, so I'm even unable to kill X or switch to a console. I'm able to ssh to system and see that X process takes 100% CPU. strace of X shows that it is receiving SIGALARM all the time. I'm using updated FC3 (xorg 6.8.2-1.FC3.13) with NVidia drivers.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open https://www.redhat.com/archives/fedora-devel-list/2005-June/msg00849.html
Actual Results: X freezes. Sometimes shift-reload required to freeze.
Expected Results: Load page
I have the exact same symptoms (X using 100% CPU, SIGALRM, etc., although my
SIGALRMs are intersperced with a lot of gettimeofday() calls, too), except my
freezes occur quite frequently when switching apps, dragging windows, etc., in
GNOME. They happen less frequently but still happen in KDE, and it doesn't
matter if I have Firefox loaded or not.
I'm on FC4 with the following Xorg packages:
I'm using the NVidia drivers, and it looks like the problem disappeared after I
set RenderAccel option to false.
Yup; same here. This can probably be closed & reported to Nvidia.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Distribution against which this bug was reported is no longer supported; could
you please reproduce this with the updated version of the currently supported
distribution (Fedora Core 6, or Fedora 7, or Rawhide)? If this issue turns out
to still be reproducible, please let us know in this bug report. If after a
month's time we have not heard back from you, we will have to close this bug as
Setting status to NEEDINFO, and awaiting information from the reporter.
Thanks in advance.