DOM Memory improvement#1770
Merged
Merged
Conversation
angelozerr
force-pushed
the
memory_improvment
branch
3 times, most recently
from
February 21, 2026 10:40
fdefe89 to
3cd1c7b
Compare
angelozerr
marked this pull request as ready for review
February 22, 2026 16:18
Signed-off-by: azerr <azerr@redhat.com>
angelozerr
force-pushed
the
memory_improvment
branch
from
February 22, 2026 16:27
3cd1c7b to
5785677
Compare
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR improves DOM memory.
If you launch DOMParserPerformance which load every time the big content.xml file you can see memory improvment (with Visual VM for instance).
Before the PR:
After the PR: