https://issues.apache.org/bugzilla/show_bug.cgi?id=56733
--- Comment #12 from Rainer Jung <rainer.j...@kippdata.de> --- As far as I understand this is not really a leak, but a high memory use. Memory allocated during a request is not freed but available for use during the next request. If you want to free high memory which might be unlikely to get used quickly again, you can set MaxMemFree 2048 2.2 has default setting MaxMemFree 0 (do not free) and 2.4 has MaxMemFree 2048 (free if 2MB are reached). This will not fix the problem of high memory need during the serving of such a request, but will free memory after the end of the request. 2.4 has optimized code, that makes the serving less memory intensive. Please report back, whether "MaxMemFree 2048" helps in your case. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
