You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by "Mukul Gandhi (JIRA)" <xe...@xml.apache.org> on 2017/11/28 05:51:00 UTC
[jira] [Resolved] (XERCESJ-1684) Very high memory usage validating
XSD 1.1 (+memory leak)
[ https://issues.apache.org/jira/browse/XERCESJ-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mukul Gandhi resolved XERCESJ-1684.
-----------------------------------
Resolution: Later
Fix Version/s: 2.12.0
Xerces's XPath 2.0 processor is hosted at https://www.eclipse.org/webtools/sse/ (Eclipse Source Editing). We're working on this branch of this project, http://git.eclipse.org/c/sourceediting/webtools.sourceediting.xpath.git/log/?h=R3_2_maintenance. We no longer have commit rights to this project. If I agree with you, that there is some issue with the Xerces's XPath 2.0 processor, then you need to reach to the pointed Eclipse project and raise your bug there. As a fix, we need to get a new JAR from Eclipse Source Editing, that we can add to our XML Schema 1.1 engine, as a fix to this issue.
> 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
> Fix For: 2.12.0
>
> 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: j-dev-unsubscribe@xerces.apache.org
For additional commands, e-mail: j-dev-help@xerces.apache.org