Red Hat Bugzilla – Bug 81341
memory leak in rhn-applet
Last modified: 2008-05-01 11:38:04 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021216
Description of problem:
I got rhn-applet working by starting with a fresh account, but found it has a
memory leak. I started noticing my machine was unreasonably slow. So I started
top and sorted by memory usage. It showed rhn-applet-gui at 50%/256mb. So I
killed it and then upgraded from 2.0.6 to 2.0.7. I was hoping the bug had gone
away, but it appears to be slowly growing in usage again. It start at 3.4, then
went to 3.1, then 4 something, then 5.4, then 5.5, and now 5.6. Plus this is
while not interacting with it at all. Comparing it to other applications like
konsole at 0.7, xchat at 1.1, evolution at 1.3, and gnome-panel at 2.2. My guess
is everytime it does a check it leaks more memory.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install rhn-applet
3. open terminal windows
4. run top
5. press M to sort by memory
Actual Results: Memory usage slowly grows
Expected Results: Memory usage to be low and at least roughly stable.
Okay, I was able to reproduce it on the beta installation,
I'm investigating, I'm afraid the exact same code does not leak
on a standard 8.0 release.
Daniel, what is the typical memory usage for the applet? 20M seems a wee bit
overkill for something that runs in the background periodically checking RHN.
5826 myohe 15 0 19992 17M 9924 S 0.3 2.3 3:42 rhn-applet-gui
Yup that may seem overkill, there is python, python bindings for a
bunch of Gnome and Gtk libraries, etc ... But otherwise coding it directly
in C mean it would take far more time to write, maintain, etc ...
Maybe once the design is solid and stable, this could be migrated to
raw C, but this would still use a lot of libraries.
Apparently upgrading to pygtk2-1.99.14-1 from RawHide fixed the problem.
It was related to a lost reference to pixmaps in the GTK Python bindings
version 1.99.13 shipped with the Beta ... I would appreciate if you can
confirm it solves the proble for you,
yes, it works after updating pygtk2.