useSelector results memory leak in child component

using this in parent component and back-forth to page, left memory uncleaned. without useselector issue is fixed.:

export function RegisterScreenFooter () {

    let footerState = useSelector((state: registration) => state.registration.footer);

https://stackoverflow.com/questions/62622168/useselector-results-memory-leak-in-child-component

[markerikson]

Yes, this.unsubscribe() is the right line.

A Subscription instance will be subscribed to either the Redux store directly, or its nearest Subscription ancestor. So, per these lines, this.unsubscribe is the subscription cleanup function that was either returned from store.subscribe(), or parentSub.addNestedSub():

https://github.com/reduxjs/react-redux/blob/a9235530f4799dd4b2acb3cc65e9caf32efbc44b/src/utils/Subscription.js#L105-L107

[phryneas]

@LaxmanPache123 you should be doing const permissions = useSelector((state) => { return state.user.permissions; }); but either way that will just lead to more rerenders, not to a memory leak. It is highly unlikely that that line is causing any kind of leak, but if it does: please read the comment above yours.

Without any reproduction (a runnable repository where we can see it happening) we cannot do anything about this.