Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
After certain time leads to Redux warning "setState() on an unmounted component"
See original GitHub issueI am testing v5 alpha from #416 and noticed that after some time every re-render in one of my components starts triggering following warning:
Can only update a mounted or mounting component. This usually means you called setState() on an unmounted component. This is a no-op. Please check the code
My best guess is that there is a memory leak somewhere and new connect holds a reference to unmounted component. Triple checked that it doesn’t happen with 4.4.5.
It doesn’t happen right away, only after I switch back and forth between routes that re-render a lot of components. I don’t have time to dig deeper and set up a test project, but I can create a branch in my public repo where it’s happening to reproduce. Please let me know if you want this.
Issue Analytics
- State:
- Created 7 years ago
- Comments:22 (15 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
react-redux-5.0.0-beta.1has been published toreact-router@next!Don’t hesitate to send a PR with minimal repro setup for the branch I created @vhmh