You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@spamassassin.apache.org by bu...@bugzilla.spamassassin.org on 2005/01/13 20:38:23 UTC
[Bug 4075] New: DBBasedAddrList->remove_entry: massive memory leak
http://bugzilla.spamassassin.org/show_bug.cgi?id=4075
Summary: DBBasedAddrList->remove_entry: massive memory leak
Product: Spamassassin
Version: 3.0.2
Platform: All
OS/Version: All
Status: NEW
Severity: critical
Priority: P3
Component: Libraries
AssignedTo: dev@spamassassin.apache.org
ReportedBy: cm@coretec.at
On line 166 in DBBasedAddrList.pm (sub remove_entry), "keys %{$self->{accum}}'
is used; this leads to ALL keys from the autowhitelist DB to be temporarily
stored in RAM at once, and with big DB files (160 MB in our case) to a SA
process memory consumption of 400MB or more.
The 'keys' construction is easily replaced by 'each', which works on the keys
one-by-one and doesn't impact the memory footprint at all.
A patch is included.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 4075] DBBasedAddrList->remove_entry: massive memory leak
Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4075
------- Additional Comments From cm@coretec.at 2005-01-13 11:39 -------
Created an attachment (id=2605)
--> (http://bugzilla.spamassassin.org/attachment.cgi?id=2605&action=view)
Patch
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
[Bug 4075] DBBasedAddrList->remove_entry: massive memory leak
Posted by bu...@bugzilla.spamassassin.org.
http://bugzilla.spamassassin.org/show_bug.cgi?id=4075
felicity@kluge.net changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|Future |3.0.3
------- Additional Comments From felicity@kluge.net 2005-01-13 11:54 -------
Yeah, that's definitely not a good thing. Moving to 3.0.3 queue.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.