[ 
https://issues.apache.org/jira/browse/XERCESJ-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Simon Sprott updated XERCESJ-1684:
----------------------------------
    Description: 
using the 1.1 code branch built from
http://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev

Using the built in sample validator 
java jaxp.SourceValidator -xsd11 -a "SAFTPT_1_04_01_XSD11_Full.xsd" -i "tmp.xml"

The validation consumes huge amounts of memory (breaks at 10 GB on my system), 
on smaller sample files validation does complete, but still consumes a very 
large quantity of memory.

Furthermore it seems to retain the memory allocated via a reference in 
org.eclipse.wst.xml.xpath2.processor.internal.DefaultRSFactory._factory after 
the validator has completed (this is not evident in the cmd line sample as the 
process ends, but I have observed in in my own code).

If I was to guess I would say that the results of the XPath queries are being 
cached via DefaultRSFactory and never released.


  was:
using the 1.1 code branch built from
http://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev

Using the built in sample validator 
java jaxp.SourceValidator -xsd11 -a "SAFTPT_1_04_01_XSD11_Full.xsd" -i "tmp.xml"

The validation consumes huge amounts of memory (breaks at 10 GB on my system), 
on smaller sample files validation does complete, but still consumes a very 
large quanity of memory.

Furthermore it seems to retain the memory allocated via a reference in 
org.eclipse.wst.xml.xpath2.processor.internal.DefaultRSFactory._factory after 
the validator has completed (this is not evident in the cmd line sample as the 
process ends, but I have observed in in my own code).



> Very high memory usage validating XSD 1.1 (+memory leak)
> --------------------------------------------------------
>
>                 Key: XERCESJ-1684
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1684
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: JAXP (javax.xml.validation)
>         Environment: windows java 1.8
>            Reporter: Simon Sprott
>            Priority: Critical
>         Attachments: SAFTPT_1_04_01_XSD11_Full.zip, tmp.zip
>
>
> using the 1.1 code branch built from
> http://svn.apache.org/repos/asf/xerces/java/branches/xml-schema-1.1-dev
> Using the built in sample validator 
> java jaxp.SourceValidator -xsd11 -a "SAFTPT_1_04_01_XSD11_Full.xsd" -i 
> "tmp.xml"
> The validation consumes huge amounts of memory (breaks at 10 GB on my 
> system), on smaller sample files validation does complete, but still consumes 
> a very large quantity of memory.
> Furthermore it seems to retain the memory allocated via a reference in 
> org.eclipse.wst.xml.xpath2.processor.internal.DefaultRSFactory._factory after 
> the validator has completed (this is not evident in the cmd line sample as 
> the process ends, but I have observed in in my own code).
> If I was to guess I would say that the results of the XPath queries are being 
> cached via DefaultRSFactory and never released.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to