[XERCESJ-1227] Poor performance / OutOfMemoryError for sequences, choices and nested with large minOccurs/maxOccurs

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 2.9.0
• Component/s: XML Schema 1.0 Structures, XML Schema 1.1 Structures
• Labels: gsoc gsoc2014 mentor
• Assignee: Unassigned
• Reporter: Michael Glavassevich
• Created: 23/Feb/07 17:11
• Updated: 15/Sep/22 20:25

Description

We now handle large minOccurs/maxOccurs on element/wildcard particles more gracefully by creating a compact representation in the DFA and using counters to check the occurence constraints, however we will still fully expand the content model for minOccurs/maxOccurs on sequences and choices which could still lead to an OutOfMemoryError or very poor performance (i.e. could still take several minutes to build the DFA). Sequences, choices and nested minOccurs/maxOccurs are somewhat tricker to handle. We would need a more general solution than the one implemented for elements and wildcards to improve those.

With the introduction of XML Schema 1.1 support we would also need to consider how to improve this for the enhanced xs:all model groups.

Issue Links

• is duplicated by: XERCESJ-1580 Out of memory while validating an XML instance with a schema that contains particles with a large maxOccurs
• is duplicated by: XERCESJ-1751 Changing maxOccurs=unbounded to some finite number throws OOM in JVM