Comment 3 for bug 841316

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.