fix: Optimize AxeBuilder memory usage.#1151
Closed
bensenescu wants to merge 1 commit into
Closed
Conversation
|
|
stephenmathieson
approved these changes
Feb 15, 2025
bensenescu
changed the title
Contributor
|
Closing for this PR to allow tests to run |
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
4 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.
If
AxeBuilderis instantiated many times, each instance of the class will store the 250kb axe source string causing performance issues.I looked at
@axe-core/puppeteerand they follow the pattern in this PR:No QA required