This repository has been archived by the owner on Jul 22, 2020. It is now read-only.
Fix jslib-modify-jquery so that it doesn't run out of memory under a fast JS engine with limited memory #12
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.
Remove nodes added by each test case every 1000 runs so that we don't end up with 1e+7 or 1e+8 nodes and use up the entire 4GB of RAM in Chromium.
To do this, changed the name of element we insert from strong to strike so that we can quickly enumerate all the elements to remove (strike doesn't appear elsewhere in the document).
Also, call after() in the test case labeled "jQuery - after()".