Bug 139491 - sa-learn has massive memory consumption
sa-learn has massive memory consumption
Product: Fedora
Classification: Fedora
Component: spamassassin (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Warren Togami
Depends On:
  Show dependency treegraph
Reported: 2004-11-16 06:05 EST by Joe Orton
Modified: 2007-11-30 17:10 EST (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-04-29 01:13:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Joe Orton 2004-11-16 06:05:23 EST
Description of problem:
run sa-learn on a ~300mb spam folder.

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

How reproducible:

Steps to Reproduce:
$ ls -lh spam-recent
-rw-------  1 joe joe 339M Nov 16 08:55 spam-recent
$ sa-learn --showdots --spam spam-recent
Actual results:
all RAM consumed

Expected results:

Additional info:
Comment 1 Joe Orton 2004-11-16 06:11:04 EST
Even with a <100mb spam folder it ate >1Gb of RAM before I killed it.
Comment 3 Joe Orton 2004-11-16 16:56:19 EST
With -3.0.1-0.EL4:

$ ls -lh spam-recent
-rw-------  1 joe joe 91M Nov 16 08:55 spam-recent
$ sa-learn --showdots --spam spam-recent

got to:

 8344 joe       25   0  943m 931m 6300 R 96.9 61.3   0:29.71 sa-learn

before I killed it again.
Comment 4 Milan Kerslager 2004-12-17 02:13:39 EST
Try to cut it to smaller pieces.
Comment 5 Warren Togami 2005-04-03 07:26:56 EDT
Please test the fc3 RPM from here, which is 3.0.2 plus upstream patches.  Some
were related to memory consumption, but it may not be related to this issue.
Comment 6 Warren Togami 2005-04-29 01:13:55 EDT
3.0.3 has been released as a FC3 update which contains one fix for massive
memory consumption, may be related to your problem.  CLOSING.  Open a new bug if
you see this problem in 3.0.3.

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