Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 427056 - Memory Leak in
Summary: Memory Leak in
Alias: None
Product: Fedora
Classification: Fedora
Component: system-config-printer
Version: 7
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F7Update
TreeView+ depends on / blocked
Reported: 2007-12-30 18:50 UTC by Ken Tanzer
Modified: 2008-01-31 09:26 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-01-31 09:26:18 UTC

Attachments (Terms of Use)

Description Ken Tanzer 2007-12-30 18:50:12 UTC
Description of problem:

We have a machine with 12GB RAM that is used by multiple users.  Several times
recently (last two weeks?) all the available RAM has been used up, and the
culprit seems to be the from system-config-printer.

This happened on Friday, and I killed all our running applet.pys, which freed up
almost all the RAM.  Today we were out of RAM again, with only 9 running
applet.pys.  Below is output indicating memory usage.  I'm reasonably sure those
numbers are in kilobytes, indicating that each process was using a gigabyte or
so of RAM.

Please note that probably none of our users actually use the applet, so the
leakage is happening while the applet just sits.

Version-Release number of selected component (if applicable):


How reproducible:
Right now, seems pretty easy.

Steps to Reproduce:
1.  Verify you have plenty of memory, and one or more users are logged in &
2.  Either watch the amount of RAM used grow, or just wait until the machine
doesn't work any more.
Actual results:
The applets use all your available memory

Expected results:
Each applet uses an amount of memory that does not grow inexorably over time,
and an amount more commensurate with being an "applet". :)

Additional info:

More detail below, but is there a good suggested workaround for this until it is

Here was the memory usage for our 9 applets:

[ktanzer@lyon ~]$ ps aux | grep pyth | grep config-printer
xxxxxxxx  3335  0.5 11.0 1515320 1383600 ?     S    Dec28  17:29 python
xxxxxxxx  3336  0.5 10.9 1515192 1369548 ?     S    Dec28  17:27 python
xxxxxxxx  3342  0.5 11.6 1515320 1452156 ?     S    Dec28  17:31 python
xxxxxxxx  3817  0.5 10.1 1504744 1271768 ?     S    Dec28  16:43 python
xxxxxxxx  3833  0.5 10.7 1504732 1345500 ?     S    Dec28  16:59 python
xxxxxxxx  3852  0.4 11.1 1504668 1385476 ?     S    Dec28  14:31 python
xxxxxxxx 12857  0.5 10.9 1486372 1362196 ?     D    Dec28  16:21 python
xxxxxxxx 16299  0.4  6.3 1096856 797272 ?      S    Dec28  14:29 python
xxxxxxxx 21289  0.5  8.4 1474740 1052156 ?     S    Dec28  15:51 python

I killed all our applets about 30 minutes ago.  One user now has an applet
running.  Here is usage (same command as for output above) from the last few

10:37:31 23432 11604
10:38:56 23812 11756
10:40:31 23944 11932
10:44:44 24412 12408
10:47:54 24744 12732

Comment 1 Tim Waugh 2008-01-02 13:19:26 UTC
Please try the current test update,

  yum --enablerepo=updates-testing update 'system-config-printer*'

Several memory leaks have been fixed in the pycups module included in that package.

Does this fix the problem?

Comment 2 Nathan Tain 2008-01-07 23:23:53 UTC
Re comment 1:
Installed the suggested update last week and that seemed to fix it.  The
processes seem to top out at 50MB of memory use.  Certainly none grew to the
huge size they did previously.

#ps aux | grep pyth | grep config-printer
50156 24692 11:25
23320 11216 12:28
50152 24912 13:10
50156 24848 14:22
23312 11236 15:00
50136 24688 15:03
50152 24904 15:49

Note You need to log in before you can comment on or make changes to this bug.