Stuck on an issue?
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.
There was no `forceUpdate`, but getting that as error message
See original GitHub issueI’m seeing lots of:
Re-rendered although props and state objects are the same. This usually means there was a call to this.forceUpdate() inside the component.
However, nowhere in those components is there a forceUpdate(). So what could that mean?
Issue Analytics
- State:
- Created 5 years ago
- Comments:19
Top Results From Across the Web
React warning about setState in unmounted component
I'm getting this error: warning.js:33 Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it ...
Read more >How and when to force a React component to re-render
Forcing an update on a React class component In any user or system event, you can call the method this. forceUpdate() , which...
Read more >How to work with React the right way to avoid some common ...
Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application....
Read more >How to force update definion on SEP clients ? | Endpoint ...
I have 5 servers with SEP Manager and much of SEP clients (500-600). Servers and clients are in separate environment (without Internet).
Read more >Avoid Memory Leak With React SetState On An Unmounted ...
Warning: Can't call setState (or forceUpdate) on an unmounted component. This is a no-op, but it indicates a memory leak in your application...
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 Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
Top Related Hashnode Post
No results found
try increasing
hotReloadBufferMswhen you patch React:https://github.com/welldone-software/why-did-you-render#options
I just wanted to confirm that for me it was related to using StrictMode