Hundreds of simultanious screensaver/kdesktop_lock processes while game open

Bug #55094 reported by jcfp
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
kdebase (Ubuntu)
Fix Released
Undecided
Rich Johnson

Bug Description

Binary package hint: kdesktop

Started up quake4 game (full screen opengl, latest nvidia driver, kubuntu 6.06, kernel-i686 on amd64)

Then instead of playing it, I went to do something more useful, and didn't use the mouse/keyboard for about 15 minutes. Result:
Hundreds of screensaver(kclock.kss) and kdesktop_lock processes using lots of resources, while no screen saver visible. See ps output below. The screensaver is set to start after 5 minutes (automatically, without password).

After I returned, the system was quite unresposive, so that it took quite some effort to close the game. The kdesktop_lock and screensaver processes had to be manually killed off afterwards.

This is reproducable with quake4, I didn't test this with other applications or other screensavers so far.

ps output after finally managing to exit the game as follows:

user 17981 9.5 1.0 37968 10392 ? S 20:41 2:40 /usr/bin/kdesktop_lock
user 17982 0.3 1.1 27100 12232 ? RN 20:41 0:05 \_ /usr/bin/kclock.kss -root
user 18061 3.5 1.0 53276 10936 ? S 20:46 0:48 /usr/bin/kdesktop_lock
user 18062 0.2 1.1 27100 12228 ? RN 20:46 0:03 \_ /usr/bin/kclock.kss -root
user 18151 1.9 1.0 53276 10432 ? S 20:51 0:21 /usr/bin/kdesktop_lock
user 18152 0.2 1.1 27096 12224 ? RN 20:51 0:02 \_ /usr/bin/kclock.kss -root
user 18230 1.1 1.0 50772 10704 ? S 20:56 0:09 /usr/bin/kdesktop_lock
user 18232 0.2 1.1 26964 12212 ? RN 20:56 0:01 \_ /usr/bin/kclock.kss -root
user 18235 1.0 1.0 51428 10612 ? S 20:56 0:07 /usr/bin/kdesktop_lock
user 18236 0.1 1.1 27100 12000 ? RN 20:56 0:01 \_ /usr/bin/kclock.kss -root
user 18239 1.0 0.9 50900 10340 ? S 20:56 0:08 /usr/bin/kdesktop_lock
user 18242 0.1 1.1 27100 12224 ? SN 20:56 0:01 \_ /usr/bin/kclock.kss -root
user 18244 1.1 1.0 47868 10368 ? S 20:56 0:08 /usr/bin/kdesktop_lock
user 18245 0.1 1.1 26640 11756 ? RN 20:56 0:01 \_ /usr/bin/kclock.kss -root
user 18249 1.1 1.0 51164 10416 ? S 20:56 0:08 /usr/bin/kdesktop_lock
user 18252 0.2 1.1 26636 11764 ? RN 20:56 0:01 \_ /usr/bin/kclock.kss -root
user 18254 1.0 1.0 51696 10504 ? S 20:56 0:07 /usr/bin/kdesktop_lock
user 18258 0.2 1.1 26636 11760 ? RN 20:56 0:01 \_ /usr/bin/kclock.kss -root
user 18261 0.9 0.9 42188 10320 ? S 20:56 0:06 /usr/bin/kdesktop_lock
user 18265 0.2 1.1 26640 11776 ? RN 20:57 0:01 \_ /usr/bin/kclock.kss -root
user 18269 1.1 1.0 37968 10684 ? S 20:57 0:07 /usr/bin/kdesktop_lock
user 18277 0.2 1.1 26636 11760 ? RN 20:57 0:01 \_ /usr/bin/kclock.kss -root
user 18279 0.8 1.0 38100 10592 ? S 20:57 0:05 /usr/bin/kdesktop_lock
user 18281 0.2 1.1 27100 12220 ? SN 20:57 0:01 \_ /usr/bin/kclock.kss -root
user 18284 0.8 1.0 37968 10572 ? S 20:57 0:05 /usr/bin/kdesktop_lock
user 18285 0.1 1.1 26636 11756 ? RN 20:57 0:01 \_ /usr/bin/kclock.kss -root
user 18288 1.0 1.0 37968 10484 ? S 20:57 0:06 /usr/bin/kdesktop_lock
user 18289 0.2 1.1 26640 11756 ? RN 20:57 0:01 \_ /usr/bin/kclock.kss -root
user 18292 1.0 1.0 37572 10448 ? S 20:58 0:07 /usr/bin/kdesktop_lock
user 18293 0.2 1.1 27100 12224 ? SN 20:58 0:01 \_ /usr/bin/kclock.kss -root
user 18296 1.1 1.0 37568 10420 ? S 20:58 0:07 /usr/bin/kdesktop_lock
user 18297 0.2 1.1 26640 11772 ? RN 20:58 0:01 \_ /usr/bin/kclock.kss -root
user 18301 1.0 1.0 37568 10688 ? S 20:58 0:07 /usr/bin/kdesktop_lock
user 18302 0.2 1.1 27096 12176 ? TN 20:58 0:01 \_ /usr/bin/kclock.kss -root
user 18305 0.9 1.0 37700 10524 ? S 20:58 0:05 /usr/bin/kdesktop_lock
user 18306 0.1 1.1 26640 11772 ? RN 20:58 0:01 \_ /usr/bin/kclock.kss -root
user 18309 0.9 1.0 38100 10540 ? S 20:58 0:06 /usr/bin/kdesktop_lock
user 18310 0.2 1.1 27096 12228 ? SN 20:58 0:01 \_ /usr/bin/kclock.kss -root
user 18313 1.1 1.0 37308 10572 ? S 20:58 0:07 /usr/bin/kdesktop_lock
user 18315 0.2 1.1 26636 11764 ? RN 20:58 0:01 \_ /usr/bin/kclock.kss -root
user 18318 0.7 1.0 37568 10824 ? S 20:58 0:04 /usr/bin/kdesktop_lock
user 18319 0.2 1.2 27100 12512 ? SN 20:58 0:01 \_ /usr/bin/kclock.kss -root
user 18322 0.9 1.0 37568 10424 ? S 20:58 0:06 /usr/bin/kdesktop_lock
user 18323 0.2 1.1 26640 11756 ? RN 20:58 0:01 \_ /usr/bin/kclock.kss -root
user 18326 0.9 0.9 38100 10320 ? S 20:58 0:05 /usr/bin/kdesktop_lock
user 18327 0.2 1.1 26640 12076 ? RN 20:58 0:01 \_ /usr/bin/kclock.kss -root
user 18330 0.8 1.0 37304 10436 ? S 20:58 0:05 /usr/bin/kdesktop_lock
user 18331 0.1 1.1 27100 12224 ? SN 20:58 0:01 \_ /usr/bin/kclock.kss -root
user 18335 0.8 1.0 37308 10592 ? S 20:58 0:05 /usr/bin/kdesktop_lock
user 18336 0.1 1.1 26640 12132 ? RN 20:58 0:01 \_ /usr/bin/kclock.kss -root
user 18339 0.8 1.0 37308 10604 ? S 20:58 0:05 /usr/bin/kdesktop_lock
user 18340 0.1 1.1 26640 12172 ? RN 20:59 0:01 \_ /usr/bin/kclock.kss -root
user 18343 0.9 0.9 37704 10188 ? S 20:59 0:05 /usr/bin/kdesktop_lock
user 18344 0.2 1.1 26636 12256 ? RN 20:59 0:01 \_ /usr/bin/kclock.kss -root
user 18347 0.8 1.0 37308 10736 ? S 20:59 0:05 /usr/bin/kdesktop_lock
user 18349 0.1 1.1 27096 12376 ? RN 20:59 0:01 \_ /usr/bin/kclock.kss -root
user 18352 0.6 1.0 37436 10672 ? S 20:59 0:03

[rest snipped. it just goes on like this for another 6 minutes]

Revision history for this message
jcfp (jcfp) wrote :

also present with other opengl games.

Revision history for this message
dvo (mueller8) wrote : Re: Hundreds of simultanious screensaver/kdesktop_lock processes

I just had the same effect on Feisty (i386), yet not with games but in connection with vmware.

Revision history for this message
Rich Johnson (nixternal) wrote :

Has anyone been able to reproduce this on either Gutsy or Hardy? Is this still an issue when playing Quake 4? All I have is Quake 3 and gave that a try and didn't see this issue. Thanks!

Changed in kdebase:
assignee: nobody → nixternal
status: New → Incomplete
Revision history for this message
jcfp (jcfp) wrote :

Will test again when I find time.

Revision history for this message
jcfp (jcfp) wrote :

Can't reproduce this one on gutsy anymore.

Revision history for this message
Jonathan Thomas (echidnaman) wrote :

Reported fixed.

Changed in kdebase:
status: Incomplete → Fix Released
Revision history for this message
Thomas Tanghus (tanghus) wrote :

Is there an upstream bug report for this? I just saw it happening on saucy. Have never experienced it before. I wasn't playing quake or anything like that.

Revision history for this message
Sergey (svs1957) wrote :

Have the same bug on trusty.
After unlock screen I see:
27625 svs 20 0 90652 9740 6380 S 2,6 0,3 21:39.52 kclock.kss
27419 svs 20 0 90388 5420 4792 S 2,3 0,2 43:15.23 kclock.kss
27719 svs 20 0 90660 9768 6396 S 2,3 0,3 20:32.12 kclock.kss
27542 svs 20 0 90644 9732 6380 S 2,0 0,3 22:00.80 kclock.kss
27764 svs 20 0 90384 5964 4788 S 2,0 0,2 40:55.50 kclock.kss
27900 svs 20 0 90388 5620 4796 S 2,0 0,2 40:41.34 kclock.kss
28310 svs 20 0 90644 9748 6396 S 2,0 0,3 14:40.17 kclock.kss
27536 svs 20 0 90396 5400 4796 S 1,7 0,2 43:20.89 kclock.kss
28489 svs 20 0 90656 9812 6448 S 1,7 0,3 14:36.90 kclock.kss
....
I never play any game. I use clock screensaver.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.