[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kscreensaver] [Bug 323064] New: Screensaver process is still running after the screensaver is gone
From:       Nick Stallman <nick () nickstallman ! net>
Date:       2013-07-31 21:33:29
Message-ID: bug-323064-17878 () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=323064

            Bug ID: 323064
           Summary: Screensaver process is still running after the
                    screensaver is gone
    Classification: Unclassified
           Product: kscreensaver
           Version: 4.10.5
          Platform: Ubuntu Packages
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: screensavers
          Assignee: kscreensaver-bugs-null@kde.org
          Reporter: nick@nickstallman.net

I've noticed screensaver processes not being killed.
There are no problems with the functionality, move the mouse and the
screensaver goes away correctly.
But the actual process doesn't exit and more importantly it looks like they are
still actually rendering the screensavers in the background.

I have 5 monitors so each time 5 separate instances of the screensaver are
created, one for each monitor (ugh looks nasty but that is another issue).
Right now grepping for 'euphoria' shows this:

nick     19808  3.8  0.2 554844 37096 ?        Sl   Jul31  32:12 euphoria
-window-id 94371957 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     19809  3.9  0.2 554844 37544 ?        Sl   Jul31  32:21 euphoria
-window-id 94371980 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     19810  3.9  0.2 555872 38084 ?        Sl   Jul31  32:48 euphoria
-window-id 94371998 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     19811  3.9  0.2 555868 38232 ?        Sl   Jul31  32:40 euphoria
-window-id 94372016 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     19812  3.9  0.2 554848 37192 ?        Sl   Jul31  32:50 euphoria
-window-id 94372034 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     20563  3.4  0.2 554844 37288 ?        Sl   Jul31  19:30 euphoria
-window-id 94371957 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     20564  3.4  0.2 554844 36904 ?        Sl   Jul31  19:29 euphoria
-window-id 94371980 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     20574  3.5  0.2 554844 37192 ?        Sl   Jul31  19:45 euphoria
-window-id 94371998 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     20581  3.5  0.2 554848 37444 ?        Sl   Jul31  19:41 euphoria
-window-id 94372016 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     20588  3.5  0.2 554848 37196 ?        Sl   Jul31  19:48 euphoria
-window-id 94372034 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     21390 15.2  0.2 555868 38360 ?        Sl   07:08   2:14 euphoria
-window-id 94371957 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     21391 15.2  0.2 554844 37292 ?        Sl   07:08   2:14 euphoria
-window-id 94371980 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     21395 16.1  0.2 554844 37460 ?        Sl   07:08   2:22 euphoria
-window-id 94371998 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     21405 16.1  0.2 554844 37200 ?        Sl   07:08   2:22 euphoria
-window-id 94372016 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3
nick     21415 16.1  0.2 554844 37376 ?        Sl   07:08   2:22 euphoria
-window-id 94372034 -i 5 -b 2 -d 25 -v 35 -s 15 -f 0 -e 1 -c 3

As you can see, my screensaver has run three times, leaving behind 15
processes. You'll notice from the CPU usage column that they are all still
running as well.

This is clearly a problem. I generally leave my computer on all the time so I
really don't want hundreds of screensavers running constantly.

Reproducible: Always

Steps to Reproduce:
1. Let screensaver trigger
2. Double check if the process has actually gone away or not
3.
Actual Results:  
Multiple processes were left running

Expected Results:  
The screensaver process should have been killed

-- 
You are receiving this mail because:
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]