The following issue has been updated:
Updater: Hans Gilde (mailto:[EMAIL PROTECTED])
Date: Sat, 18 Sep 2004 9:37 PM
Comment:
Here's a demonstration of the problem.
Also, I'm working on a fix that will keep the one-tag-inplementation-per-thread system
that Jelly wants, while stopping the memory leak.
The only thing is that the current use of ThreadLocal in TagScript doesn't look to me
like it should cause a memory leak. Odd.
Changes:
Attachment changed to thread-local-memory-leak.zip
---------------------------------------------------------------------
For a full history of the issue, see:
http://issues.apache.org/jira/browse/JELLY-148?page=history
---------------------------------------------------------------------
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: Sat, 18 Sep 2004 9:37 PM
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]
