Paul, your activemath.org account isn't working.

This looks good for the memory leak but... if we're going to change the API,
why not just store the cache in the JellyContext and be done with it?

-----Original Message-----
From: Paul Libbrecht [mailto:[EMAIL PROTECTED] 
Sent: Friday, December 17, 2004 4:11 PM
To: Hans Gilde
Subject: Memory-leak test seems to go through


Hey Hans,

This mail will arrive probably too late as I am offline now but... 
anyways... just to let you know that my TagHolderMap thread-local seems 
to succeed with the memory-leak test that you have proposed. I'd like 
it if you can confirm it.
Careful, I had to explicitly add 
        
org.apache.commons.jelly.impl.TagScript.clearTagHolderMap(); at line 
118 of BaseMemoryLeak until I find the good places to put this 
clearing.
I don't like to put it even in the parser's returned ScriptBlock's run 
as I anticipate this reference will play the role of the session within 
some more elaborate setting (like my reloadable tags)... advice is 
welcome there.
(in a sense, an approach would be to have a trace of when the 
tagReferenceMap was created so that it becomes the place when it's 
removed...).

paul


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

Reply via email to