apr-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 40955] - possible apr_allocator_max_free_set issues
Date Wed, 22 Nov 2006 16:06:03 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=40955>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=40955


jorton@redhat.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|allocator_free may leak     |possible
                   |nodes                       |apr_allocator_max_free_set
                   |                            |issues




------- Additional Comments From jorton@redhat.com  2006-11-22 08:06 -------
Per dev@apr mail:

The issues Brian reference look real but are entirely unrelated to the
symptoms you have described - they cannot cause a "memory leak" in your
app.  If the memory use in your app is increasing *indefinitely* then
that's a pool memory misuse problem.

Check that e.g. all pools you create are also destroyed and that no
memory is being allocated out of long-lived pools by whatever operation
it is you see consuming memory.

I'll leave this bug open to track the _max_free_set issues Brian points out.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Mime
View raw message