Collectives™ on Stack Overflow
Find centralized, trusted content and collaborate around the technologies you use most.
Learn more about Collectives
Teams
Q&A for work
Connect and share knowledge within a single location that is structured and easy to search.
Learn more about Teams
Problem
I am writing an application in React and was unable to avoid a super common pitfall, which is calling
setState(...)
after
componentWillUnmount(...)
.
I looked very carefully at my code and tried to put some guarding clauses in place, but the problem persisted and I am still observing the warning.
Therefore, I've got two questions:
How do I figure out from the stack trace
, which particular component and event handler or lifecycle hook is responsible for the rule violation?
Well, how to fix the problem itself, because my code was written with this pitfall in mind and is already trying to prevent it, but some underlying component's still generating the warning.
Browser console
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 the componentWillUnmount
method.
in TextLayerInternal (created by Context.Consumer)
in TextLayer (created by PageInternal) index.js:1446
d/console[e]
index.js:1446
warningWithoutStack
react-dom.development.js:520
warnAboutUpdateOnUnmounted
react-dom.development.js:18238
scheduleWork
react-dom.development.js:19684
enqueueSetState
react-dom.development.js:12936
./node_modules/react/cjs/react.development.js/Component.prototype.setState
react.development.js:356
_callee$
TextLayer.js:97
tryCatch
runtime.js:63
invoke
runtime.js:282
defineIteratorMethods/</prototype[method]
runtime.js:116
asyncGeneratorStep
asyncToGenerator.js:3
_throw
asyncToGenerator.js:29
import { throttle } from 'lodash';
import * as React from 'react';
import { AutoWidthPdf } from '../shared/AutoWidthPdf';
import BookCommandPanel from '../shared/BookCommandPanel';
import BookTextPath from '../static/pdf/sde.pdf';
import './Book.css';
const DEFAULT_WIDTH = 140;
class Book extends React.Component {
setDivSizeThrottleable: () => void;
pdfWrapper: HTMLDivElement | null = null;
isComponentMounted: boolean = false;
state = {
hidden: true,
pdfWidth: DEFAULT_WIDTH,
constructor(props: any) {
super(props);
this.setDivSizeThrottleable = throttle(
() => {
if (this.isComponentMounted) {
this.setState({
pdfWidth: this.pdfWrapper!.getBoundingClientRect().width - 5,
componentDidMount = () => {
this.isComponentMounted = true;
this.setDivSizeThrottleable();
window.addEventListener("resize", this.setDivSizeThrottleable);
componentWillUnmount = () => {
this.isComponentMounted = false;
window.removeEventListener("resize", this.setDivSizeThrottleable);
render = () => (
<div className="Book">
{ this.state.hidden && <div className="Book__LoadNotification centered">Book is being loaded...</div> }
<div className={this.getPdfContentContainerClassName()}>
<BookCommandPanel
bookTextPath={BookTextPath}
<div className="Book__PdfContent" ref={ref => this.pdfWrapper = ref}>
<AutoWidthPdf
file={BookTextPath}
width={this.state.pdfWidth}
onLoadSuccess={(_: any) => this.onDocumentComplete()}
<BookCommandPanel
bookTextPath={BookTextPath}
getPdfContentContainerClassName = () => this.state.hidden ? 'hidden' : '';
onDocumentComplete = () => {
try {
this.setState({ hidden: false });
this.setDivSizeThrottleable();
} catch (caughtError) {
console.warn({ caughtError });
export default Book;
AutoWidthPdf.tsx
import * as React from 'react';
import { Document, Page, pdfjs } from 'react-pdf';
pdfjs.GlobalWorkerOptions.workerSrc = `//cdnjs.cloudflare.com/ajax/libs/pdf.js/${pdfjs.version}/pdf.worker.js`;
interface IProps {
file: string;
width: number;
onLoadSuccess: (pdf: any) => void;
export class AutoWidthPdf extends React.Component<IProps> {
render = () => (
<Document
file={this.props.file}
onLoadSuccess={(_: any) => this.props.onLoadSuccess(_)}
pageNumber={1}
width={this.props.width}
</Document>
class Book extends React.Component {
setDivSizeThrottleable: ((() => void) & Cancelable) | undefined;
pdfWrapper: HTMLDivElement | null = null;
state = {
hidden: true,
pdfWidth: DEFAULT_WIDTH,
componentDidMount = () => {
this.setDivSizeThrottleable = throttle(
() => {
this.setState({
pdfWidth: this.pdfWrapper!.getBoundingClientRect().width - 5,
this.setDivSizeThrottleable();
window.addEventListener("resize", this.setDivSizeThrottleable);
componentWillUnmount = () => {
window.removeEventListener("resize", this.setDivSizeThrottleable!);
this.setDivSizeThrottleable!.cancel();
this.setDivSizeThrottleable = undefined;
render = () => (
<div className="Book">
{ this.state.hidden && <div className="Book__LoadNotification centered">Book is being loaded...</div> }
<div className={this.getPdfContentContainerClassName()}>
<BookCommandPanel
BookTextPath={BookTextPath}
<div className="Book__PdfContent" ref={ref => this.pdfWrapper = ref}>
<AutoWidthPdf
file={BookTextPath}
width={this.state.pdfWidth}
onLoadSuccess={(_: any) => this.onDocumentComplete()}
<BookCommandPanel
BookTextPath={BookTextPath}
getPdfContentContainerClassName = () => this.state.hidden ? 'hidden' : '';
onDocumentComplete = () => {
try {
this.setState({ hidden: false });
this.setDivSizeThrottleable!();
} catch (caughtError) {
console.warn({ caughtError });
export default Book;
–
Solution
You can declare let isMounted = true inside useEffect, which will be changed in the cleanup callback, as soon as the component is unmounted. Before state updates, you now check this variable conditionally:
useEffect(() => {
let isMounted = true; // note mutable flag
someAsyncOperation().then(data => {
if (isMounted) setState(data); // add conditional check
return () => { isMounted = false }; // cleanup toggles value, if unmounted
}, []); // adjust dependencies to your needs
const Parent = () => {
const [mounted, setMounted] = useState(true);
return (
Parent:
<button onClick={() => setMounted(!mounted)}>
{mounted ? "Unmount" : "Mount"} Child
</button>
{mounted && <Child />}
Unmount Child, while it is still loading. It won't set state later on,
so no error is triggered.
const Child = () => {
const [state, setState] = useState("loading (4 sec)...");
useEffect(() => {
let isMounted = true;
fetchData();
return () => {
isMounted = false;
// simulate some Web API fetching
function fetchData() {
setTimeout(() => {
// drop "if (isMounted)" to trigger error again
// (take IDE, doesn't work with stack snippet)
if (isMounted) setState("data fetched")
else console.log("aborted setState on unmounted component")
}, 4000);
}, []);
return <div>Child: {state}</div>;
ReactDOM.render(<Parent />, document.getElementById("root"));
<script src="https://cdnjs.cloudflare.com/ajax/libs/react/16.13.0/umd/react.production.min.js" integrity="sha256-32Gmw5rBDXyMjg/73FgpukoTZdMrxuYW7tj8adbN8z4=" crossorigin="anonymous"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/react-dom/16.13.0/umd/react-dom.production.min.js" integrity="sha256-bjQ42ac3EN0GqK40pC9gGi/YixvKyZ24qMP/9HiGW7w=" crossorigin="anonymous"></script>
<div id="root"></div>
<script>var { useReducer, useEffect, useState, useRef } = React</script>
Extension: Custom useAsync Hook
We can encapsulate all the boilerplate into a custom Hook, that automatically aborts async functions in case the component unmounts or dependency values have changed before:
function useAsync(asyncFn, onSuccess) {
useEffect(() => {
let isActive = true;
asyncFn().then(data => {
if (isActive) onSuccess(data);
return () => { isActive = false };
}, [asyncFn, onSuccess]);
// custom Hook for automatic abortion on unmount or dependency change
// You might add onFailure for promise errors as well.
function useAsync(asyncFn, onSuccess) {
useEffect(() => {
let isActive = true;
asyncFn().then(data => {
if (isActive) onSuccess(data)
else console.log("aborted setState on unmounted component")
return () => {
isActive = false;
}, [asyncFn, onSuccess]);
const Child = () => {
const [state, setState] = useState("loading (4 sec)...");
useAsync(simulateFetchData, setState);
return <div>Child: {state}</div>;
const Parent = () => {
const [mounted, setMounted] = useState(true);
return (
Parent:
<button onClick={() => setMounted(!mounted)}>
{mounted ? "Unmount" : "Mount"} Child
</button>
{mounted && <Child />}
Unmount Child, while it is still loading. It won't set state later on,
so no error is triggered.
const simulateFetchData = () => new Promise(
resolve => setTimeout(() => resolve("data fetched"), 4000));
ReactDOM.render(<Parent />, document.getElementById("root"));
<script src="https://cdnjs.cloudflare.com/ajax/libs/react/16.13.0/umd/react.production.min.js" integrity="sha256-32Gmw5rBDXyMjg/73FgpukoTZdMrxuYW7tj8adbN8z4=" crossorigin="anonymous"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/react-dom/16.13.0/umd/react-dom.production.min.js" integrity="sha256-bjQ42ac3EN0GqK40pC9gGi/YixvKyZ24qMP/9HiGW7w=" crossorigin="anonymous"></script>
<div id="root"></div>
<script>var { useReducer, useEffect, useState, useRef } = React</script>
More on effect cleanups: Overreacted: A Complete Guide to useEffect
–
–
–
–
–
To remove - Can't perform a React state update on an unmounted component warning, use componentDidMount method under a condition and make false that condition on componentWillUnmount method. For example : -
class Home extends Component {
_isMounted = false;
constructor(props) {
super(props);
this.state = {
news: [],
componentDidMount() {
this._isMounted = true;
ajaxVar
.get('https://domain')
.then(result => {
if (this._isMounted) {
this.setState({
news: result.data.hits,
componentWillUnmount() {
this._isMounted = false;
render() {
–
–
–
–
–
componentWillUnmount() {
// fix Warning: Can't perform a React state update on an unmounted component
this.setState = (state,callback)=>{
return;
–
–
–
There is a hook that's fairly common called useIsMounted that solves this problem (for functional components)...
import { useRef, useEffect } from 'react';
export function useIsMounted() {
const isMounted = useRef(false);
useEffect(() => {
isMounted.current = true;
return () => isMounted.current = false;
}, []);
return isMounted;
then in your functional component
function Book() {
const isMounted = useIsMounted();
useEffect(() => {
asyncOperation().then(data => {
if (isMounted.current) { setState(data); }
–
–
Checking if a component is mounted is actually an anti pattern as per React documentation. The solution to the setState warning is rather to leverage on the use of an AbortController:
useEffect(() => {
const abortController = new AbortController() // creating an AbortController
fetch(url, { signal: abortController.signal }) // passing the signal to the query
.then(data => {
setState(data) // if everything went well, set the state
.catch(error => {
if (error.name === 'AbortError') return // if the query has been aborted, do nothing
throw error
return () => {
abortController.abort() // stop the query by aborting on the AbortController on unmount
}, [])
For asynchronous operations that aren't based on the Fetch API, there still should be a way to cancel these asynchronous operations, and you should rather leverage these than just checking if a component is mounted. If you are building your own API, you can implement the AbortController API in it to handle it.
For more context, the check if a component is mounted is an anti pattern as React is checking internally if the component is mounted to display that warning. Doing the same check again is just a way to hide the warning, and there are some easier ways to hide them than adding this piece of code on a big part of a codebase.
Source: https://medium.com/doctolib/react-stop-checking-if-your-component-is-mounted-3bb2568a4934
–
I had this warning possibly because of calling setState from an effect hook (This is discussed in these 3 issues linked together).
Anyway, upgrading the react version removed the warning.
React already removed this warning
but here is a better solution (not just workaround)
useEffect(() => {
const abortController = new AbortController() // creating an AbortController
fetch(url, { signal: abortController.signal }) // passing the signal to the query
.then(data => {
setState(data) // if everything went well, set the state
.catch(error => {
if (error.name === 'AbortError') return // if the query has been aborted, do nothing
throw error
return () => {
abortController.abort()
}, [])
–
–
The solution from @ford04 didn't worked to me and specially if you need to use the isMounted in multiple places (multiple useEffect for instance), it's recommended to useRef, as bellow:
Essential packages
"dependencies":
"react": "17.0.1",
"devDependencies": {
"typescript": "4.1.5",
My Hook Component
export const SubscriptionsView: React.FC = () => {
const [data, setData] = useState<Subscription[]>();
const isMounted = React.useRef(true);
React.useEffect(() => {
if (isMounted.current) {
// fetch data
// setData (fetch result)
return () => {
isMounted.current = false;
–
if (this.isComponentMounted) {
this.setState({
pdfWidth: this.pdfWrapper!.getBoundingClientRect().width - 5,
{ leading: false, trailing: true }
–
I know that you're not using history, but in my case I was using the useHistory hook from React Router DOM, which unmounts the component before the state is persisted in my React Context Provider.
To fix this problem I have used the hook withRouter nesting the component, in my case export default withRouter(Login), and inside the component const Login = props => { ...; props.history.push("/dashboard"); .... I have also removed the other props.history.push from the component, e.g, if(authorization.token) return props.history.push('/dashboard') because this causes a loop, because the authorization state.
An alternative to push a new item to history.
Add a ref to a jsx component and then check it exist
function Book() {
const ref = useRef();
useEffect(() => {
asyncOperation().then(data => {
if (ref.current) setState(data);
return <div ref={ref}>content</div>
I had a similar issue thanks @ford04 helped me out.
However, another error occurred.
NB. I am using ReactJS hooks
ndex.js:1 Warning: Cannot update during an existing state transition (such as within `render`). Render methods should be a pure function of props and state.
What causes the error?
import {useHistory} from 'react-router-dom'
const History = useHistory()
if (true) {
history.push('/new-route');
return (
<render component />
This could not work because despite you are redirecting to new page all state and props are being manipulated on the dom or simply rendering to the previous page did not stop.
What solution I found
import {Redirect} from 'react-router-dom'
if (true) {
return <redirect to="/new-route" />
return (
<render component />
–
If you are fetching data from axios and the error still occurs, just wrap the setter inside the condition
let isRendered = useRef(false);
useEffect(() => {
isRendered = true;
axios
.get("/sample/api")
.then(res => {
if (isRendered) {
setState(res.data);
return null;
.catch(err => console.log(err));
return () => {
isRendered = false;
}, []);
If you are used hook and useEffect, So put a return end of useEffect.
useEffect(() => {
window.addEventListener('mousemove', logMouseMove)
return () => {
window.removeEventListener('mousemove', logMouseMove)
}, [])
componentWillUnmount:
If you are used componentDidMount, So put componentWillUnmount next to it.
componentDidMount() {
window.addEventListener('mousemove', this.logMouseMove)
componentWillUnmount() {
window.removeEventListener('mousemove', this.logMouseMove)
The isMounted approach is an anti-pattern in most cases because it doesn't actually clean up/cancel anything, it just avoids changing state on unmounted components, but does nothing with pending asynchronous tasks. The React team recently removed the leak warning because users keep creating a lot of anti-patterns to hide the warning rather than fix its cause.
But writing cancellable code in plain JS can be really tricky. To fix this I made my own lib useAsyncEffect2 with custom hooks, built on top of a cancellable promise (c-promise2) for executing cancellable async code to reach its graceful cancellation. All async stages (promises), including deep ones, are cancellable. This means that the request here will be automatically aborted if its parent context is canceled. Of course, any other asynchronous operation can be used instead of a request.
useAsyncEffect Demo with plain useState usage (Live Demo):
import React, { useState } from "react";
import { useAsyncEffect } from "use-async-effect2";
import cpAxios from "cp-axios";
function TestComponent({url}) {
const [text, setText] = useState("");
const cancel = useAsyncEffect(
function* () {
setText("fetching...");
const json = (yield cpAxios(url)).data;
setText(`Success: ${JSON.stringify(json)}`);
[url]
return (
<div>{text}</div>
<button onClick={cancel}>
Cancel request
</button>
useAsyncEffect Demo with internal states usage (Live Demo):
import React from "react";
import { useAsyncEffect } from "use-async-effect2";
import cpAxios from "cp-axios";
function TestComponent({ url, timeout }) {
const [cancel, done, result, err] = useAsyncEffect(
function* () {
return (yield cpAxios(url).timeout(timeout)).data;
{ states: true, deps: [url] }
return (
{done ? (err ? err.toString() : JSON.stringify(result)) : "loading..."}
<button onClick={cancel} disabled={done}>
Cancel async effect (abort request)
</button>
Class component using decorators (Live demo)
import React, { Component } from "react";
import { ReactComponent } from "c-promise2";
import cpAxios from "cp-axios";
@ReactComponent
class TestComponent extends Component {
state = {
text: ""
*componentDidMount(scope) {
const { url, timeout } = this.props;
const response = yield cpAxios(url).timeout(timeout);
this.setState({ text: JSON.stringify(response.data, null, 2) });
render() {
return (<div>{this.state.text}</div>);
export default TestComponent;
More other examples:
Axios request with errors handling
Fetch weather by coords
Live search
Pause & Resume
Progress capturing
Edit: I just realized the warning is referencing a component called TextLayerInternal. That's likely where your bug is. The rest of this is still relevant, but it might not fix your problem.
1) Getting the instance of a component for this warning is tough. It looks like there is some discussion to improve this in React but there currently is no easy way to do it. The reason it hasn't been built yet, I suspect, is likely because components are expected to be written in such a way that setState after unmount isn't possible no matter what the state of the component is. The problem, as far as the React team is concerned, is always in the Component code and not the Component instance, which is why you get the Component Type name.
That answer might be unsatisfactory, but I think I can fix your problem.
2) Lodashes throttled function has a cancel method. Call cancel in componentWillUnmount and ditch the isComponentMounted. Canceling is more "idiomatically" React than introducing a new property.
–
–
UPDATE DO NOT USE MY ORIGINAL ANSWER AS IT DOES NOT WORK
This answer was based on the use of cancelable promises and a note in makecancelable which I migrated to use hooks. However, it appears it does not cancel a chain of async/await and even cancelable-promise does not support canceling of a chain of awaits
Doing a bit more research on this, it appears that some internal Google reasons prevented cancelable promises from coming into the standard.
Further more, there was some promise with Bluebird which introduces cancelable promises, but it does not work in Expo or at least I haven't seen an example of it working in Expo.
The accepted answer is the best. Since I use TypeScript I had adapted the code with a few modifications (I explicitly set the dependencies since the accepted answer's implicit dependencies appear to give a re-render loop on my app, added and use async/await rather than promise chain, pass a ref to the mounted object so that an async/await chain can be canceled earlier if needed)
* This starts an async function and executes another function that performs
* React state changes if the component is still mounted after the async
* operation completes
* @template T
* @param {(mountedRef: React.MutableRefObject<boolean>) => Promise<T>} asyncFunction async function,
* it has a copy of the mounted ref so an await chain can be canceled earlier.
* @param {(asyncResult: T) => void} onSuccess this gets executed after async
* function is resolved and the component is still mounted
* @param {import("react").DependencyList} deps
export function useAsyncSetEffect(asyncFunction, onSuccess, deps) {
const mountedRef = useRef(false);
useEffect(() => {
mountedRef.current = true;
(async () => {
const x = await asyncFunction(mountedRef);
if (mountedRef.current) {
onSuccess(x);
})();
return () => {
mountedRef.current = false;
}, deps);
Original answer
Since I have many different operations that are async, I use the cancelable-promise package to resolve this issue with minimal code changes.
Previous code:
useEffect(() =>
(async () => {
const bar = await fooAsync();
setSomeState(bar);
})(),
New code:
import { cancelable } from "cancelable-promise";
useEffect(
() => {
const cancelablePromise = cancelable(async () => {
const bar = await fooAsync();
setSomeState(bar);
return () => cancelablePromise.cancel();
You can alsowrpte it in a custom utility function like this
* This wraps an async function in a cancelable promise
* @param {() => PromiseLike<void>} asyncFunction
* @param {React.DependencyList} deps
export function useCancelableEffect(asyncFunction, deps) {
useEffect(() => {
const cancelablePromise = cancelable(asyncFunction());
return () => cancelablePromise.cancel();
}, deps);
In my case of a login-like screen, the fetch was done in a onClick handler of a parent component, who passed that handler down to the child, whom placed .catch and .finally on it.
In the .then case a redirect (and hence unmount) would happen as normal operation, and only in cases of fetch error would the child stay mounted on-screen.
My solution was moving the setState and all other code from the .finally to the .catch since the child is guaranteed to be mounted in the .catch case. And in the .then case nothing needed doing because of the guaranteed unmount.
Based on @ford04 answer, here is the same encapsulated in a method :
import React, { FC, useState, useEffect, DependencyList } from 'react';
export function useEffectAsync( effectAsyncFun : ( isMounted: () => boolean ) => unknown, deps?: DependencyList ) {
useEffect( () => {
let isMounted = true;
const _unused = effectAsyncFun( () => isMounted );
return () => { isMounted = false; };
}, deps );
Usage:
const MyComponent : FC<{}> = (props) => {
const [ asyncProp , setAsyncProp ] = useState( '' ) ;
useEffectAsync( async ( isMounted ) =>
const someAsyncProp = await ... ;
if ( isMounted() )
setAsyncProp( someAsyncProp ) ;
return <div> ... ;
–
–
Here is a simple solution for this. This warning is due to when we do some fetch request while that request is in the background (because some requests take some time.)and we navigate back from that screen then they react cannot update the state. here is the example code for this. write this line before every state Update.
if(!isScreenMounted.current) return;
Here is the Complete Code
import React , {useRef} from 'react'
import { Text,StatusBar,SafeAreaView,ScrollView, StyleSheet } from 'react-native'
import BASEURL from '../constants/BaseURL';
const SearchScreen = () => {
const isScreenMounted = useRef(true)
useEffect(() => {
return () => isScreenMounted.current = false
},[])
const ConvertFileSubmit = () => {
if(!isScreenMounted.current) return;
setUpLoading(true)
var formdata = new FormData();
var file = {
uri: `file://${route.params.selectedfiles[0].uri}`,
type:`${route.params.selectedfiles[0].minetype}`,
name:`${route.params.selectedfiles[0].displayname}`,
formdata.append("file",file);
fetch(`${BASEURL}/UploadFile`, {
method: 'POST',
body: formdata,
redirect: 'manual'
}).then(response => response.json())
.then(result => {
if(!isScreenMounted.current) return;
setUpLoading(false)
}).catch(error => {
console.log('error', error)
return(
<StatusBar barStyle="dark-content" />
<SafeAreaView>
<ScrollView
contentInsetAdjustmentBehavior="automatic"
style={styles.scrollView}>
<Text>Search Screen</Text>
</ScrollView>
</SafeAreaView>
export default SearchScreen;
const styles = StyleSheet.create({
scrollView: {
backgroundColor:"red",
container:{
flex:1,
justifyContent:"center",
alignItems:"center"
I solved this problem by providing all the params that are used in the useEffect hook
The code reported the bug:
useEffect(() => {
getDistrict({
geonameid: countryId,
subdistrict: level,
}).then((res) => {
......
}, [countryId]);
The code after fix:
useEffect(() => {
getDistrict({
geonameid: countryId,
subdistrict: level,
}).then((res) => {
......
}, [countryId,level]);
Can see that , problems solved after I provided all the params(including the level param) that supposed to pass through.
I have sifted trough the answers on this fairly popular question and now I get where my juniors and mids all got the same idea how to handle this problem.
Firstly it needs to be said this answer relies on "post hooks" react. I tend to enforce that style over the old one because more readability and less boilerplate. If you prefer the React components over functional ones, I am not gonna argue, you do you, I will focus on the functional components/hooks solution.
Sadly I have to say that the "You can declare let isMounted = true inside useEffect, which will be changed in the cleanup and all the similar answers offering some variance of isMounted" is in fact wrong. It works but not in a way one might expect.
It simply MOVES the check that React is ALREADY DOING before the place in timeline when React does it. That is it. The result is React now not showing you a warning. This is actually an ANTIPATTERN.
So what, warning got hidden - no harm no foul?
You have invested time, you have expanded codebase, that IS SOMETHING and achieved nothing. Well, not entirely nothing, WORSE that nothing, you have removed legitimate warning telling you to optimize your code and effectively scrub it under the carpet where it still lives the same life(cycle -pun intended) as before.
Oke, so what is so bad about it living?
It causes memory leaks.
Your application still runs those queries AND wastes cycles and once it has finished doing so it does not use results.
Now that you are familiar with what is the result of that "solution" you have to choose. If this did not alarm you, fair enough, please at the minimum remove that ridiculous warning hiding code and at least keep the codebase clean.
If you got all riled up how you overlooked it and are willing to find a better solution, let's go:
CASE 1. If the async part of the app causing this is actually API queries, you should cancel your requests.If you are not using you should seriously consider using FetchAPI and then you can use AbortControllerAPI. Yes it is that simple and there are numerous other advantages over XMLHttpRequest.
In code (using FetchAPI) it looks like this:
const controller = new AbortController();
const { signal } = controller;
fetch("http://localhost:8000", { signal }).then(response => {
console.log(`Request 1 is complete!`);
}).catch(e => {
console.warn(`Fetch 1 error: ${e.message}`);
fetch("http://localhost:8000", { signal }).then(response => {
console.log(`Request 2 is complete!`);
}).catch(e => {
console.warn(`Fetch 2 error: ${e.message}`);
// Wait 2 seconds to abort both requests
// Hopefully you have not set your timeout lower than that somehow or it will fire before this
// catch will still fire off but the caught error would be different
setTimeout(() => controller.abort(), 2000);
Notice - when you cancel the request - the catch handlers fire off instead the actual response handlers that would process the data, set state etc.
(don't notice I stole the code from David Walsh cause it is simple, well known solution, and most importantly - I am lazy)
NOTE:
I get what you are saying but I use Axios / legacy code uses Axios and it uses XMLHttpRequest.
True, it does, but it enhances it with the cancel mechanism. Just google axios.CancelToken and find out.
Or, use Ky. It is IMHO basically better axios, based on FetchAPI which is superior API.
CASE 2. The async code causing this problem is NOT API queries therefore there is no built in cancel mechanisms.
Well, WRITE ONE :) You are a programmer, aren't you?
NOTE:
Deadline is coming, this is the last thing I needed, additional thinking and code, there is no time to think, I need sleep not additional work. I am just gonna hide it.
There, there, it will be oke - try:
Check if the lib you are using already has its own (like axios or
fileReaderAPI).
The before mentioned AbortControllerAPI works in most browsers and NodeJS.
Ignore the warning, don't be a prick and mask it :)
I had a similar problem and solved it :
I was automatically making the user logged-in by dispatching an action on redux
( placing authentication token on redux state )
and then I was trying to show a message with this.setState({succ_message: "...")
in my component.
Component was looking empty with the same error on console : "unmounted component".."memory leak" etc.
After I read Walter's answer up in this thread
I've noticed that in the Routing table of my application ,
my component's route wasn't valid if user is logged-in :
{!this.props.user.token &&
<Route path="/register/:type" exact component={MyComp} />
I made the Route visible whether the token exists or not.
In my case the issue was that the parent component was hidding the child because of a condition change in the child component.
So what I did was to change the condition so the child component was always shown.
What was happening:
const ParentComponent:FC = () => {
if (someCondition) {
return null;
return (
Some cool text here
<ChildModalComponent message="this is a cool modal" />
const ChildModalComponent: FC = () => {
const handleSubmit = () => {
setSomeCondition(true);
So after clicking submit the modal was automatically hidden becasue of the parent condition (someCondition).
How did I fix it?
I changed the place where the someCondition was checked in the Parent component, so the child component was always shown:
const ParentComponent:FC = () => {
return (
{!someCondition && <>Some cool text here</>
<ChildModalComponent message="this is a cool modal" />
I faced same warning, not it is fixed. To fix the issue, I removed the useRef() variable check in useEffect()
Earlier, the code was
const varRef = useRef();
useEffect(() => {
if (!varRef.current)
}, []);
Now, the code is
const varRef = useRef();
useEffect(() => {
//if (!varRef.current)
}, [])
Hope, it helps...
Can't perform a React state update on an unmounted component
this error message is very clear. one example would be this
try {
setIsLoading(true);
... you run some logic
unmountingCode
setError(null);
} catch (error) {
setError(error.message);
this kind of try/catch logic is very common for UI control. we run some logic, then we unmoun the current component and then we are setting state with setError(null). this will create the above error message. to fix this, set the state first and then unmount
setError(null);
unmountingCode
This is typically happening when running setState after waiting for an asynchronous function. If the component is no longer mounted when the response arrives, attempting to set state when the response arrives will result in the error message you are seeing.
useEffect(
() => {
someAsyncFunction().then(data => {
setData(data) // ❌ unsafe call of setData
We can fix this by setting a local flag in the effect, and using the effect clean-up function to switch the flag when the component unmounts. The Fetching Data guide from the React docs has more details -
useEffect(
() => {
let mounted = true // ✅ component is mounted
someAsyncFunction().then(data => {
if (mounted) setData(data) // ✅ setState only if mounted
return () => {
mounted = false // ✅ component is unmounted
custom hook, no callbacks
But can you imagine writing all of that each time you needed to run an asynchronous function in one of your components? Thankfully we can easily encapsulate this logic in a custom hook.
Other answers here provide a clumsy API that ask the user to specify onSuccess or onError callbacks. This reminds me of the code everyone was writing before we had promises. Let's see if we can do better -
import { DependencyList, useEffect, useState } from "react"
type UseAsyncHookState<T> =
| { kind: "loading" }
| { kind: "error", error: Error }
| { kind: "result", data: T }
function useAsync<T>(func:() => Promise<T>, deps: DependencyList) {
const [state, setState] = useState<UseAsyncHookState<T>>({ kind: "loading" })
useEffect(
() => {
let mounted = true
func()
.then(data => mounted && setState({ kind: "result", data }))
.catch(error => mounted && setState({ kind: "error", error }))
return () => {
mounted = false
deps,
return state
Our hook helps us detangle complex API logic from component state and lifecycle. With a well-defined type and simple API method -
type User = { … }
async function getUser(id: number): Promise<User> {
return …
We can write our component in declarative way, without the need for callbacks -
function UserProfile(props: { userId: number }) {
const user = useAsync( // ✅ type automatically inferred
() => getUser(props.userId), // async call
[props.userId], // dependencies
switch (user.kind) { // ✅ exhaustive switch..case
case "loading":
return <Loading />
case "result":
return <UserData user={user.data} />
case "error":
return <Error message={user.error.message} />
This also takes advantage of TypeScript 5's new switch..case exhaustive completions, ensuring that our component correctly checks for all state possibilities of the hook.
vanilla javascript
For non-TypeScript users, here's the vanilla hook that does the exact same thing -
import { useState, useEffect } from "react"
function useAsync(func, deps) {
const [state, setState] = useState({ kind: "loading" })
useEffect(
() => {
let mounted = true
func()
.then(data => mounted && setState({ kind: "result", data }))
.catch(error => mounted && setState({ kind: "error", error }))
return () => {
mounted = false;
return state
For me I got this issue while my app open another page meanwhile it gets all the data after login; I mean in my function login I set states of account before I get company data causing my app switcher to load CreateComapnyApp component before the process was accomplished
Here is how my login function was before
const login = React.useCallback(
async ({ username, password }) => {
const accountData = await getAccountData(token)
setAccount(accountData)
let companyData = null
if (accountData.is_verified) {
companyData = await getCompanyByUser(accountData.id)
setCompany(companyData)
return accountData
[getAccountData, setAccount, setCompany, setToken],
These is the app switcher
function AppSwitcher() {
const { account, company } = useAuth()
if (account?.is_verified && !company) {
return <CreateCompanyApp />
if (account?.is_verified && company) {
return <AuthenticatedApp />
return <UnAuthenticatedApp />
Explanation setAccount(accountData) causes the app to re-render so the condition if (account?.is_verified && !company) is verified the component CreateCompanyApp is rendered after that login continue processing and get company data now if (account?.is_verified && company) is verified, this setAccount before getting company data what caused Can't perform a React state update on an unmounted component issue
The solution is simply to move setAccount after getting company data so the condition if (account?.is_verified && company) is verified directly
const login = React.useCallback(
async ({ username, password }) => {
const accountData = await getAccountData(token)
let companyData = null
if (accountData.is_verified) {
companyData = await getCompanyByUser(accountData.id)
setAccount(accountData) //here we go
setCompany(companyData)
return accountData
[getAccountData, setAccount, setCompany, setToken],
Inspired by the accepted answer by @ford04 I had even better approach dealing with it, instead of using useEffect inside useAsync create a new function that returns a callback for componentWillUnmount :
function asyncRequest(asyncRequest, onSuccess, onError, onComplete) {
let isMounted=true
asyncRequest().then((data => isMounted ? onSuccess(data):null)).catch(onError).finally(onComplete)
return () => {isMounted=false}
useEffect(()=>{
return asyncRequest(()=>someAsyncTask(arg), response=> {
setSomeState(response)
},onError, onComplete)
},[])
–
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
