gDesklets

gdesklets launches python2 which slowly accumulates memory

Bug #841316 reported by john
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gDesklets
Triaged
Undecided
gDesklets Core Team
Fedora
Fix Released
Undecided

Bug Description

gdesklets appears to be running normally. but i noticed by running 'top' that python 2 was consuming over 3 gigs of ram by itself. when i killed the python2 process, the gdesklet application closes. I have restarted gdesklets with and without desklets running and the result is the same, a slow but steady climb in memory being consumed by python2.

Revision history for this message
Bjoern Koch (h.humpel) wrote :

Is this the same bug as #190894 or #198401 ?

Changed in gdesklets:
assignee: nobody → gDesklets Core Team (gdesklets-core-team)
status: New → Triaged
Revision history for this message
In , Carl-Johan (carl-johan-redhat-bugs) wrote :

Description of problem:
I have a slight suspicion that gdesklets-daemon has a memory leak.
$ ps u 4403
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
cjk 4403 0.9 44.9 7028448 5538828 ? Dl Oct12 92:26 python /usr/lib64/gdesklets/gdesklets-daemon

6.3 GB is a bit much.

Version-Release number of selected component (if applicable):
gdesklets-0.36.3-2.fc15.x86_64
python-2.7.1-7.fc15.x86_64

I'm running the calendar, the clock and CrispClock.

I have tried restarting all the desklets but that didn't give back any RAM.

Revision history for this message
In , Luya (luya-redhat-bugs) wrote :

Hello,
Memory leak seems to be related to python 2 as reported by upstream which investigates the issue.

Revision history for this message
Ronny Lorenz (raumzeit) wrote :

Should be #190894.
I also experienced several gigs of wasted memory with only two displays.
For a fix for this leak that worked at least for me, see comment #8 in #190894

Revision history for this message
In , Carl-Johan (carl-johan-redhat-bugs) wrote :

Memory leak still there in F16.

Revision history for this message
In , Luya (luya-redhat-bugs) wrote :

Added patch from Launchpad bug report, please test to see if the leak still occurs.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

gdesklets-0.36.3-6.1.fc16 has been submitted as an update for Fedora 16.
https://admin.fedoraproject.org/updates/gdesklets-0.36.3-6.1.fc16

Revision history for this message
In , Luya (luya-redhat-bugs) wrote :

*** Bug 702518 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Luya (luya-redhat-bugs) wrote :

*** Bug 727352 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

Package gdesklets-0.36.3-6.1.fc16:
* should fix your issue,
* was pushed to the Fedora 16 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing gdesklets-0.36.3-6.1.fc16'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-5537/gdesklets-0.36.3-6.1.fc16
then log in and leave karma (feedback).

Revision history for this message
In , Carl-Johan (carl-johan-redhat-bugs) wrote :

I have tried the update and I can't see it leaking any more memory. Seems the bug has been fixed.

Revision history for this message
In , Luya (luya-redhat-bugs) wrote :

Could you leave karma on the link from #7? Thanks.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

gdesklets-0.36.3-6.1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/gdesklets-0.36.3-6.1.fc15

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

gdesklets-0.36.3-6.1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.

Revision history for this message
In , Fedora (fedora-redhat-bugs) wrote :

gdesklets-0.36.3-6.1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.

Bug Watch Updater (bug-watch-updater)
Changed in fedora:
importance: Unknown → Undecided
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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