[AutoComplete] setState called even when component unmounted

[ghost]

[AutoComplete]:SetState Called even when component unmounted

on handleNewRequest mounted new component

Versions

• Material-UI: 0.15.2
• React: 0.14.6
• Browser: Chrome 51.0.2704.103

I have autocomplete of which handleNewRequest event I am mounting a new component.I get a error that its called setState for searchText.How do I Prevent this.

I have tried to call setState on componentWillUnmount by taking the searchText in my state.Still not solved

Images & references

It has something to do with timerTouchTapCloseId.
it calls

_this.setState({
   searchText: searchText
});

which it cannot find once unmounted

[chenwei0104]

+1

[ghost]

I have a workaround.If we add a delay of 100ms it works fine.

[oliviertassinari]

@dhruvdatt I have noticed the same thing when playing with the AutoComplete. I haven't investigated much. Looks like one of the componentWillUnmount method isn't clearing the asynchronous dependencies correctly.

[dbroadhurst]

I'm seeing the same issue when I navigate from a screen using the onChange method on a DropDown menu

[avocadowastaken]

This problem comes from Popover, some race condition problem.

Maybe it's good idea to not maintains stuffs like that and focus on main the thing UI and let third party libs maintain positioning and visibility. I found react-overlays super useful

[chrisshiplet]

Running into this issue as well. setTimeout callbacks like the one in Popover that call setState on a component should always be referenced on the component instance (something like this.timer), so you can call clearTimeout(this.timer) when the component unmounts. Otherwise the callback will try to update state after the component is gone.

Related: https://facebook.github.io/react/blog/2015/12/16/ismounted-antipattern.html

[oliviertassinari]

Closed by #4783