Closed
Conversation
Contributor
|
Fixes software-mansion/react-native-reanimated#7647 as well. |
Member
|
Thanks! We should really use a different data structure than ShadowView in AttributedString... |
Collaborator
|
This pull request was successfully merged by @mobinni in 5229e50 When will my fix make it into a release? | How to file a pick request? |
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
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.
Summary:
When implementing a local FPS monitor I noticed that
TextInputleaked memory. @tomekzaw helped triage and confirm whether the leak was occurring in reanimated or react-native upstream.We collaborated on a fix for this and noticed that this was fixed 6 years ago in text here
We've ported the same fix to
BaseTextInputShadowNode.hChangelog:
[General] [Fixed] - Fix memory leak in TextInput
Test Plan:
https://snack.expo.dev/@mobinni/memory-leak-reproducer