tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 37793] - org.apache.jasper.runtime.BodyContentImpl doesn't reset the 'cb' character array, causes memory leak
Date Mon, 05 Dec 2005 20:28:35 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=37793>.
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=37793





------- Additional Comments From pyou@vignette.com  2005-12-05 21:28 -------
Turning off tag pooling (i.e, set 'enablePooling' initial parameter to 'false' 
for the JSP page compiler and execution servlet) doesn't turning off the 
PageContext pooling in JspFactoryImpl class. The 'USE_POOL' is set to 'true' 
and can not be overwritten:

   private static final boolean USE_POOL = true;

I am really interested to know the rationale behind the decision of not re-
sizing the 'cb' character array on setWriter(). If the 'cb' array grows huge by 
one tag evaluation, its massive memory block will not be returned to heap until 
the Jasper runtime is restarted. The merit of this behavior is questionable at 
least.

-- 
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.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org


Mime
View raw message