Add memory stress tests for JSObject and JSClosure #399
Conversation
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
Tests memory exhaustion, heap fragmentation, and boundary conditions without FinalizationRegistry to validate reference counting under extreme allocation pressure.
kateinoigakukun
force-pushed
the
add-stress-tests-for-jsobject-jsclosure
branch
from
f8f5291 to
42e879f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
Memory management bugs in JavaScript interop often only surface under extreme allocation pressure (see PR #393 which required 10-30 million allocations to reproduce). Current tests only validate normal usage patterns and don't catch memory leaks or reference counting issues that appear at system boundaries.
Summary
Adds comprehensive stress tests that push memory allocation to limits and test system behavior under extreme pressure to catch real memory management bugs.
Test Coverage
Implementation
Tests use aggressive garbage collection and expect/handle memory exhaustion failures to validate reference counting mechanisms under stress.