Bug 429332

Summary:	"boxed" screensave hogs 99% CPU and hangs the GUI
Product:	[Fedora] Fedora	Reporter:	Charles R. Anderson <cra>
Component:	xscreensaver	Assignee:	Mamoru TASAKA <mtasaka>
Status:	CLOSED RAWHIDE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-04-04 04:48:57 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 Charles R. Anderson 2008-01-18 19:00:57 UTC

Description of problem:
In Screensaver Preferences, simply selecting the "Boxed" screensaver theme
causes the GUI to lock up.  You can move the mouse, but you cannot move any
windows, click on any menus, change TTYs, or do anything at all basically. 
SSHing into the box reveals that "boxed" is taking all the CPU.

Version-Release number of selected component (if applicable):
xscreensaver-gl-extras-5.04-3.fc9

How reproducible:
didn't try

Steps to Reproduce:
1. Open Screensaver Preferences
2. Click on "Boxed"

Actual results:
GUI hangs.  Boxed takes 99% CPU.

Comment 1 Mamoru TASAKA 2008-01-19 03:12:00 UTC

Well, I have not investigated this however,

- Is it simply that boxes is using much CPU? On my box boxed is
  working good, however it usually costs 50% of CPU.
  Actually some hacks in xscreensaver-gl-extras use much CPU.
  Would you write the spec of your box?

- And would you check if your GL is actually working (by
  glxinfo in glx-utils, for example)? For me rawhide mesa-libGL is 
  simply not working so for now I am using F-8 mesa-libGL.
  Also for me rawhide X is not working so I am using F-8 X.

Comment 2 Mamoru TASAKA 2008-02-17 17:25:51 UTC

Once setting NEEDINFO.

Comment 3 Charles R. Anderson 2008-04-04 04:48:57 UTC

No longer seeing this issue.