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 Wed, 13 Oct 2004 04:42:51 GMT
The following comment has been added to this issue:

     Author: Hans Gilde
    Created: Tue, 12 Oct 2004 9:41 PM
Guido, I agree with your ideas in principal. However, for 1.0 we don't want to change the
API, especially to replace it with a potentially less stable API.

Going forward, we will undoubtedly have a discussion on the proper API to use. Maybe you could
file a new issue in jira containing your suggestion? This way, we can hash out the API and
implement something more stable in a future release.
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: Tue, 12 Oct 2004 9:41 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