StAX Streaming Parser and DOM Tree Builder Interoperability: Memory Footprint at Integration Boundary

Direct answer

StAX supplies events on demand while DOM retains every node until removed; the integration boundary risks unbounded heap growth if every parsed element is converted to a DOM node without discarding processed subtrees. No standard DOM API limits node creation during streaming—the filter must live in the StAX layer. Whether peak heap stays bounded depends on the size and retention pattern of the DOM subset you need to keep in memory.

Confirmed facts

• StAX is a pull parser and does not hold the source document in memory.
• W3C DOM implementations retain every instantiated node in memory until it is explicitly removed and garbage-collected.
• The W3C DOM API provides no built-in mechanism to cap node creation during a stream; selection must be enforced by the caller.

Likely explanation for unbounded growth

When code converts every START_ELEMENT into a DOM node and retains references, the tree grows proportionally to the full document size, regardless of the streaming nature of StAX.

Steps needed for this case

1. Use XMLStreamReader to iterate events and test each START_ELEMENT against the exact subset of elements you must retain as DOM.
2. For matching elements, create a detached DocumentFragment, copy attributes and text content, process the fragment immediately, then remove it from its parent and null all references before advancing the cursor.
3. Configure the JVM heap with -Xmx sized for the expected fragment set plus parser buffers, not for the full 100 MB document.

JVM GC configurations that have been observed to reduce OutOfMemoryError risk in similar concurrent parsing scenarios include using G1GC or ZGC, and tuning -XX:InitiatingHeapOccupancyPercent to trigger concurrent marking earlier. Exact pause and throughput characteristics vary by JVM vendor and workload.

Missing diagnostic detail: What is the expected size and retention pattern of the DOM subset you need to keep in memory? If you must retain most of the document as DOM, no streaming hybrid can keep peak heap below the DOM tree size, and a different architecture is required.