You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by "Hans Gilde (JIRA)" <co...@jakarta.apache.org> on 2004/12/16 03:46:02 UTC
[jira] Commented: (JELLY-148) Huge memory leak resulting from the use of ThreadLocal
[ http://nagoya.apache.org/jira/browse/JELLY-148?page=comments#action_56749 ]
Hans Gilde commented on JELLY-148:
----------------------------------
There's some problem with the patch for this issue, see JELLY-85
I'm looking into it.
> Huge memory leak resulting from the use of ThreadLocal
> ------------------------------------------------------
>
> Key: JELLY-148
> URL: http://nagoya.apache.org/jira/browse/JELLY-148
> Project: jelly
> Type: Bug
> Components: core / taglib.core
> Versions: 1.0
> Reporter: Hans Gilde
> Priority: Critical
> Fix For: 1.0
> Attachments: jelly-nothreadlocal.ZIP, jelly-nothreadlocal2.ZIP, memory-leak-junit-test.txt, thread-local-memory-leak-fix-demo-parent.txt, thread-local-memory-leak-fix-demo.txt, thread-local-memory-leak-fix-final-1.txt, thread-local-memory-leak-fix-final-xml-tags.txt, thread-local-memory-leak-fix-final.txt, thread-local-memory-leak-profile.zip, thread-local-memory-leak.zip
>
> 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:
http://nagoya.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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org