Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 154205 - CPU continuously pegged at 100%, appears to be by gdm-binary
Summary: CPU continuously pegged at 100%, appears to be by gdm-binary
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 4
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2005-04-08 12:46 UTC by
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-04-08 13:45:15 UTC

Attachments (Terms of Use)

Description 2005-04-08 12:46:00 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

Description of problem:
Extemely poor system performance noted after installation of FC4Test1 when switching to graphical desktop.  Once desktop finally loads mouse response is great as is desktop menu (right mouse click on desktop).  However, EVERYTHING else runs EXTREMELY slow.  All apps take forever to load.  System Monitor takes 45+ seconds to appear.  CPU is pegged continuously at 100%. Process list shows "gdm-binary", "syslogd" and "X" continuously appearing every couple of seconds at 100% CPU.  Throughout all this, the mouse is still very responsive but nothing else is.  Like it is, the system is completely unusable for anything other than moving the cursor around the screen.  My system processor is an AMD Sempron 2200+.

Version-Release number of selected component (if applicable):
Fedora Core 4 Test 1 (complete installation)

How reproducible:

Steps to Reproduce:
1. Boot the system and wait for the desktop to appear.

Additional info:

Comment 1 Ray Strode [halfline] 2005-04-08 13:45:15 UTC
This got fixed shortly after test1 went out.  You can repair the problem on your
machine by upgrading to the latest gdm in rawhide or by waiting until test2
which should be out pretty soon.

The rawhide rpm is here:

Note You need to log in before you can comment on or make changes to this bug.