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
Allows disposing of unused Blob data when JS garbage collection takes place.
Type of Change
Why
Continuous instantiation of
Blob
JavaScript objects can lead to memory leaks because the disposal of those objects does not trigger the deallocation of the blob data on the native side (seeIBlobPersistor
).For further context:
fetch
more than a certain number of times in React Native facebook/react-native#39441What
Microsoft::React::BlobCollector
.Blob
instance lifetime and cleans up its corresponding blob data on destruction.__blobCollectorProvider
through JSI.Important: This fix only applies to the TurboModule variant.
We need to figure out a way to set this up for the Blob CxxModule, which requires accessing its
facebook::jsi::Runtime
instance reference.Testing
Use proof of concept https:/jurocha-ms/Repro/tree/blobmemleak/ReactNative/fetchwinleak (see README).
Microsoft Reviewers: Open in CodeFlow