Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 80069 - kernel is "leaking" memory
Summary: kernel is "leaking" memory
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Raw Hide
Classification: Retired
Component: kernel
Version: 1.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Dave Jones
QA Contact: Brian Brock
URL:
Whiteboard:
Depends On:
Blocks: 79579 CambridgeTarget
TreeView+ depends on / blocked
 
Reported: 2002-12-19 15:34 UTC by Manfred Hollstein
Modified: 2015-01-04 22:02 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-10-30 03:51:40 UTC
Embargoed:

Attachments (Terms of Use)

Description Manfred Hollstein 2002-12-19 15:34:27 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021203

Description of problem:
I put kernel-2.4.20-1 (plus all required dependencies hwdata, kudzu,
mkinitrd, modutils) on my otherwise up2date 8.0 system, booted and
watched the swap space constantly growing... The funny thing is, that
it starts allocating swap even when plenty of RAM is still free.
Right after booting and after logging in using Gnome, free shows 24MB
swap already being allocated with appr. 420MB free RAM left (the system
has 512MB RAM). One can then fire up top and sit there watching
allocated swap growing and growing :-(

FWIW, using a vanilla 2.4.20 plus Alan's ac2 patch does not show
this behaviour.

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

How reproducible:
Always

Steps to Reproduce:
1.Install listed RPMs
2.Boot system
3.Watch memory data reported by the "free" program (or use "top")
    

Actual Results:  Allocated swap space is constantly growing, even when nothing
is actively running on the system.

Expected Results:  No swap space should be allocated, in other words memory
usage should remain constant if nothing is running on the system.

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