DO NOT REPLY [Bug 15845] - 4.1.19 Memory Leak when creating compilier for JSP pages

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15845>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=15845

4.1.19 Memory Leak when creating compilier for JSP pages

jakarta@trollingers.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|WONTFIX                     |
            Summary|Memory Leak when compiling  |4.1.19 Memory Leak when
                   |JSP                         |creating compilier for JSP
                   |                            |pages
            Version|4.1.14                      |4.1.19



------- Additional Comments From jakarta@trollingers.com  2003-01-16 15:24 -------
there is still a memory leak in 4.1.19

it is not the compile itself that causes the leak, but the 
JspCompilationContext being stored with is compilier indefinatly.  

I have tracked to down somewhat if you read below there is a way to fix it, but 
not sure of the side effects it might have.  the culprit seems to be the code 
that checks all the includes to see if they have changed.  it appears to hold 
on the the jspcompilationcontext in a map, and never gets rid of the map so the 
more jsp pages you compile the bigger that map gets and the more memory that is 
taken up.

please someone take a serious look at this.  I know some of you think the 
solution is to precomile every thing, but that is not always posible.

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>