commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Commented: (JELLY-148) Huge memory leak resulting from the use of ThreadLocal
Date Mon, 27 Sep 2004 00:33:32 GMT
The following comment has been added to this issue:

     Author: Hans Gilde
    Created: Sun, 26 Sep 2004 5:33 PM
In terms of its affect on Maven, this issue affects anyone who compiles and runs many Jelly
scripts over the course of their application. This is most noticed by Servlet users that execute
Jelly scripts on every Servlet request, all in the same JVM.

Any Maven script that compiles and runs hundreds of sub scripts over the course of its execution
should notice an increase in memory use. I suspect that no one has noticed this because people
don't really care if their Maven script eats an extra 2 megs of memory, since it will exit

Also, this bug has been in Jelly for a while, so I doubt that Maven users have been impacted.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: JELLY-148
    Summary: Huge memory leak resulting from the use of ThreadLocal
       Type: Bug

     Status: Unassigned
   Priority: Critical

    Project: jelly
             core / taglib.core

   Reporter: Hans Gilde

    Created: Sat, 18 Sep 2004 9:34 PM
    Updated: Sun, 26 Sep 2004 5:33 PM

There is a huge memory leak that results from the TagScript's use of ThreadLocal.

ThreadLocal is usually used from a staic variable, while TagScript uses it from an instance
variable. Although this looks legal to me, it causes a huge memory leak.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message