Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application.
See original GitHub issueHi.
Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.
I’m using logout hook now, but it didn’t clean up inside useEffect, causing memory leak. (ref)
In addition, google scripts are being added every time a component is re-rendered.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:10
- Comments:19 (4 by maintainers)
Top Results From Across the Web
Can't perform a React state update on an unmounted ...
I am writing an application in React and was unable to avoid a super common pitfall, which is calling setState(...) after componentWillUnmount(.
Read more >How to fix the React memory leak warning - DEV Community
Warning : Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in...
Read more >Can't perform a React state update on an unmounted ... - GitHub
Warning : Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in...
Read more >Can't perform a React state update on an unmounted ... - Reddit
Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application....
Read more >React state update on an unmounted component - debuggr.io
Warning : Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Still getting memory leaks warning
Any update on this?