After certain time leads to Redux warning "setState() on an unmounted component"

[Restuta]

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

[max-mykhailenko]

I have the same issue

[jimbolla]

A repro would be very helpful. Thanks.

[Restuta]

@max-mykhailenko do you have simple steps to repro?

[timdorr]

@Restuta Do you have a reproducible test case as well?

Does this occur in the canonical real-world example? https://github.com/reactjs/redux/tree/master/examples/real-world

[Restuta]

@timdorr not it does not, I created a branch that you can use to repro it.

Branch: https://github.com/Restuta/rcn.io/tree/react-redux-connect-bug

Steps to repro:

• git clone git@github.com:Restuta/rcn.io.git
• cd rcn.io
• npm i && npm run dev
• open http://localhost:8888/events/8 in your browser
• open console
• click on MTB in the header and then back to "Event 8"

You should see in console:

"Warning: setState(...): 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 for the Connect(EventDetails) component."

Notice that the only change from "dev" branch is bump of redux-react and you can test it yourself that issue is not happening with 4.4.5. @jimbolla

[jimbolla]

Thanks, I'll have a look at this tonight.

[jimbolla]

@Restuta That git repo address doesn't seem to work for me. Is it supposed to be https://github.com/Restuta/rcn.io.git?

[Restuta]

@jimbolla that address is in SSH format, of you prefer HTTPS then yes, use that one

[jimbolla]

I have a fix ready for this here but I'm going to attempt to write a test for it before submitting the PR. Honestly, writing the test is the hard part for me. 😆

[vhmth]

@jimbolla what do you think the timeline is for getting this in? This is the last thing before #465 gets in, which is causing some UI issues for our beta users so I'm more than happy to write some tests if you're feeling tied up. :-)