Mailing List Archive

------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

http://www.exim.org/bugzilla/show_bug.cgi?id=504





------- Comment #2 from holmgren@lysator.liu.se 2007-05-21 10:54 -------
There's some information on Exim's memory handling in
http://www.exim.org/exim-html-4.66/doc/html/spec_html/ch42.html#SECTmemhanloc
and http://www.exim.org/viewvc/exim/exim-src/src/store.c .

There is only one long-lived Exim process, namely the daemon process. Care has
been taken to ensure that it doesn't leak memory. All queue runners, message
reception processes, etc. are forked from it when they aren't run separately
(e.g. from inetd, cron, or the command line), are short-lived, and can't
affect its memory usage. Because of that, it doesn't matter much that not all
memory is freed, although as you noted, the memory containing the acl_m
variables is freed before the next message is received in an SMTP session.

In short, your report doesn't seem to describe a bug, or even a problem.

--
Configure bugmail: http://www.exim.org/bugzilla/userprefs.cgi?tab=email

--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##

------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

http://www.exim.org/bugzilla/show_bug.cgi?id=504





------- Comment #3 from michael.reynolds@sosdg.org 2007-05-21 11:14 -------
It might not be a significant, if any, problem now, but the potential is there
for it to become a problem. (When has memory management *not* become a problem
in the long run for *any* software?) This is why I reported it now.
Preventative maintenance and all that.

--
Configure bugmail: http://www.exim.org/bugzilla/userprefs.cgi?tab=email

--
## List details at http://www.exim.org/mailman/listinfo/exim-dev Exim details at http://www.exim.org/ ##