[XERCESJ-1684] Very high memory usage validating XSD 1.1 (+memory leak)

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Later
• Fix Version/s: 2.12.0
• Component/s: JAXP (javax.xml.validation)
• Environment: windows java 1.8
• Assignee: Unassigned
• Reporter: Simon Sprott
• Created: 06/Nov/17 09:16
• Updated: 28/Nov/17 14:56
• Resolved: 28/Nov/17 05:50

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.

Issue Links

• is duplicated by: XERCESJ-1686 Very high memory usage validating XSD 1.1 (+memory leak)