DO NOT REPLY [Bug 32836] New: - memory retention

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=32836>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=32836

           Summary: memory retention
           Product: Security
           Version: cvs
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Signature
        AssignedTo: security-dev@xml.apache.org
        ReportedBy: sylvain@dusart.org


Tested with Sun jdk 1.4.2_05 (with the right jars in the endorsed dirs) and 1.5.0.

I updated the VerifySignature sample class with the signature file
data/ie/baltimore/merlin-examples/merlin-xmldsig-fifteen/signature-enveloping-rsa.xml
   to add a loop (2000 iterations) before the line with the XML parsing (and
removed the try catch to stop at the first exception).

An OutOfMemoryError is systematically thrown (after 816 iterations here at home
 in eclipse, java heap size : 128 Mb).

After some investigations, the ThreadLocal in CachedXPathAPIHolder seems to be
responsible for the memory retention.

I updated this class to get :

public CachedXPathAPI getCachedXPathAPI() {
        return new CachedXPathAPI();
}

and the problem was solved (a quick but not really smart fix, I admit ;) ).

With the loop AFTER the xml parsing in VerifySignature, there was no problem.
That is to say the memory retention occurs when verifying signatures of
different org.w3c.dom.Document objects (maybe something similar to bug 29595 in
class CachedXPathAPI, did not take time to look for further explanations...).

Sylvain.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.