The real fix is to initialize ap_max_mem_free to APR_ALLOCATOR_MAX_FREE_UNLIMITED during the pre_config hook in each of the MPMs. Unless there are any objections, I will check this in shortly. I assume that this also needs to be back ported to httpd-2.0.
Brad Brad Nicholes Senior Software Engineer Novell, Inc., the leading provider of Net business solutions http://www.novell.com >>> "Sander Striker" <[EMAIL PROTECTED]> Tuesday, August 26, 2003 5:34:00 PM >>> > From: Jean-Jacques Clar [mailto:[EMAIL PROTECTED] > Sent: Tuesday, August 26, 2003 2:01 AM > Cliff, > Are you waiting for other OSs testing on that fix or it is ready to be checked in? > One thing I found annoying is that MAXMEMFREE is not reset to the default value on a server restart > when commenting out the directive in the config file. The default value being the equivalent of unlimited? > Looks like the function ap_mpm_set_max_mem_free() is, by design, called > only if the directive is present. Brad just told me that should be easily > fixed by inserting a function call to sets ap_max_mem_free during the core_post_config > step to use either a value from the config file or the default one. > > What do you think? It seems like not resetting the max mem free on the allocator on config reload is a bug. So +1. Sander
mpminit.patch
Description: Binary data
