Bug 90760
Summary: | Screensavers consuming too much CPU | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Michael Waite <mwaite> |
Component: | xscreensaver | Assignee: | Bill Nottingham <notting> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 7.3 | CC: | rvokal, tao |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2003-06-19 18:07:47 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Michael Waite
2003-05-13 14:11:16 UTC
Many of the screensavers try to draw as fast as possible... this will cause them to use CPU. If this is not desired, pick a different one, or, for instance, a blank screen. The GX260-related problems sound like graphics card specific issues. For the record, *none* of the screensavers try to draw as fast as possible: all of them (by default) spend enough time in usleep() that they should not be loading the system significantly. Plus, xscreensaver runs all of them at a low priority with nice. (The unfortunate exception to this is the case of OpenGL hacks running on systems without GL hardware, in which case, the X server itself tremendously loads the machine.) However, it would be normal for a screensaver to consume 80%+ of the CPU -- if the CPU would otherwise have been *completely idle*. That is, the saver should never make the load go above 1.0, though *approaching* 1.0 would be expected. Closing as not a bug; as jwz said things are acting more or less as designed. |