fix(Regions): prevent memory leak on region removal #4258
Merged
+179
−7
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.
Description
This PR fixes issue #4243 where regions were not properly garbage collected after calling
region.remove().Implementation Details
Root Cause
When
region.remove()was called, the region object remained in memory because:Solution
addEventListenercalls with the codebase's existingfromEventpattern for better consistency and automatic cleanupremove()method - Added comprehensive cleanup for:unAll()How to Test It
Automated Tests
Manual Testing
region.remove()Checklist
Fixes #4243