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.

setState called on unmounted component

See original GitHub issue

I gotten a error where MediaQuery are trying to call setState on a unmounted component.

Issue Analytics

State:
Created 5 years ago
Reactions:1
Comments:10 (3 by maintainers)

Top GitHub Comments

2reactions

hoschicommented, Nov 1, 2018

@contra I got again access to a Mac and can confirm that 6.0.0 fixes the problem. Thanks! 💯

0reactions

yocontracommented, Oct 28, 2018

Should be fixed in 6.0.0

Top Results From Across the Web

Avoid Memory Leak With React SetState On An Unmounted ...

Specifically, calling setState() in an unmounted component means that your app is still holding a reference to the component after the component ......

React - setState() on unmounted component - Stack Overflow

This usually means you called setState() on an unmounted component. This is a no-op. Please check the code for the undefined component.

Prevent React setState on unmounted Component

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....

Prevent React setState on unmounted component - Martin Belev

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...

React: Stop checking if your component is mounted - Medium

Like most React developers, you have probably encountered at least once in your life the “setState warning”: Warning: Can't perform a React ...