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 Fri, 24 Sep 2004 14:42:32 GMT
The following comment has been added to this issue:

     Author: peter royal
    Created: Fri, 24 Sep 2004 7:40 AM
option #3 (WeakRef) would mean no changes to JellyContext then, right? I'm all for no explicit
API changes, but requiring people to keep explicit references to a Script when they want to
re-use parts of it later.

(the blissed project, does something like that.. you have a Jelly
script that builds a model, and pieces of the model may included subsets of the script to
be executed later. Currently the initial Script is thrown away after evaluation but with the
WeakRef change, we'd just need to keep a handle to it and all would be well)
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: Fri, 24 Sep 2004 7:40 AM

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