The following comment has been added to this issue:

     Author: Guido Anzuoni
    Created: Tue, 21 Sep 2004 4:25 AM
       Body:
About dion comment.

It seems to me that is hard to have the TagScript data not in
JellyContext without the risk of memory leaks.
Even if my comments might be caused by a quite imprecise
understanding of "what" a TagScript represents (the xml tag as 
***literally*** resumed by parser ?) and "what" a Tag represents
(the TagScript with the attributes' values expressions 
evaluated against the context ?).
But, if my assumptions are correct than, I think, Tags should
disapper as soon as the JellyContext disappers.
And a JellyContext should disappear when no more references to
it are held by an application.

About JellyContext.
There are some Map members with Hashtable instances as
JellyContext could be used in multi-threaded environment.
If so, quite hard. Otherwise use HashMap for performances.

---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/JELLY-148?page=comments#action_53276

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/JELLY-148

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
 Components: 
             core / taglib.core
   Versions:
             1.0-beta-5

   Assignee: 
   Reporter: Hans Gilde

    Created: Sat, 18 Sep 2004 9:34 PM
    Updated: Tue, 21 Sep 2004 4:25 AM

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


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to