[kellarwindland]

Summary:
AndroidTextInputShadowNode::getAttributedString builds the fragment for a controlled value with parentShadowView = ShadowView(*this). A full ShadowView carries the node's current state and props. updateStateIfNeeded stores that attributed string in the next AndroidTextInputState (reactTreeAttributedString), so every new state keeps the previous state (and props) alive. The chain grows by one link per value change for as long as the input stays mounted.

Two effects:

• Memory: native heap grows with every change to a controlled TextInput and is only released on unmount.
• Crash: on unmount the whole chain is destroyed recursively on the JS thread. Long chains overflow the stack, and crash stacks repeat State → AttributedString → Fragment → ShadowView → State dozens of times before ending in a SIGSEGV in ~AndroidTextInputState().

D94267721 fixed the same retain chain for iOS/macOS by adding shadowViewFromShadowNode() in BaseTextInputShadowNode.h. AndroidTextInputShadowNode does not inherit from BaseTextInputShadowNode, so Android still had the bug.

This change clears props and state on the parent ShadowView before storing it in the fragment, mirroring the iOS fix. On Android, parentShadowView is only read for tag, componentHandle and layoutMetrics. Its state and props are never read.

Changelog:

[Android] [Fixed] - Fix memory leak in TextInput: each state retained the previous one, which could overflow the stack on unmount

Differential Revision: D131297146

[meta-codesync]

@kellarwindland has exported this pull request. If you are a Meta employee, you can view the originating Diff in D131297146.

[javache]

Review automatically exported from Phabricator review in Meta.