Bug 753441

Summary: xscreensaver too cpu intensive - look for replacement.
Product: [Fedora] Fedora Reporter: jurek.bajor
Component: lxde-commonAssignee: Christoph Wickert <cwickert>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 16CC: cwickert
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-12 17:51:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description jurek.bajor 2011-11-12 14:54:06 UTC
Description of problem:
Is it necessary to ship a package in which some screen savers are so CPU
intensive and causing excessive temperature comtrol ?
Also a problem for power consumption.

Time to look for a light X screen saver and locker.

xscreensaver is too cpu intensive, and also too heavy (MB).

Version-Release number of selected component (if applicable):
 xscreensaver-base            i686     1:5.15-3.fc16        @updates     1.3 M
 xscreensaver-extras          i686     1:5.15-3.fc16        @updates     6.5 M
 xscreensaver-extras-base     i686     1:5.15-3.fc16        @updates     182 k

How reproducible:
Menu - Preferences - Screensaver

Steps to Reproduce:
1. as above
2. test screen savers
3.
  
Actual results:

Select m6502 from Random Screen Saver
Almost immediately the system is very busy (m6502's %CPU around 75) and soon
temperature control jumps in.
$ top
top - 14:50:06 up  1:01,  1 user,  load average: 0.39, 0.30, 0.16
Tasks: 104 total,   2 running, 102 sleeping,   0 stopped,   0 zombie
Cpu(s):  1.0%us,  1.3%sy, 74.9%ni, 22.4%id,  0.0%wa,  0.0%hi,  0.3%si,  0.0%st
Mem:    759804k total,   472376k used,   287428k free,    22384k buffers
Swap:  1171764k total,        0k used,  1171764k free,   293828k cached

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 1512 jb        30  10  7392 4056 1720 R 75.2  0.5   0:47.73 m6502
  878 root      20   0 31632  10m 6488 S  1.7  1.4   0:34.86 X
 1447 root      20   0     0    0    0 S  0.3  0.0   0:00.10 kworker/0:2
 1506 jb        20   0  2856 1116  892 R  0.3  0.1   0:00.29 top
    1 root      20   0  5456 3328 1948 S  0.0  0.4   0:01.64 systemd
    2 root      20   0     0    0    0 S  0.0  0.0   0:00.00 kthreadd
    3 root      20   0     0    0    0 S  0.0  0.0   0:00.10 ksoftirqd/0

Also bad examples: XAnalogTV, XLyap, XRaySwarm, Zoom, etc.

Expected results:
Screen saver easy on system, temperature, and power consumption/management.

Additional info:

Comment 1 Christoph Wickert 2011-11-12 17:51:07 UTC
So? None of this screensavers is installed or configured by default in LXDE. The reason why we choose xscreensaver is it's functionality and security model. For more info please refer to http://www.jwz.org/xscreensaver/versus-xlock.html and http://www.jwz.org/xscreensaver/faq.html

Feel free to reopen this bug once you come up with an alternative that can compete with xscreensaver.