Cancel the timer in beforedestroyed:
The reason is that instead of simply resize after each redraw, a component is re-instantiated. Due to the independence of Data, the timer in the new component = null, while the timer in the old component always exists and has not been destroyed. At this time, the seals instance has been destroyed, so there will be a warning that the seals instance has been destroyed
Similar Posts:
- [Solved] Error: `resize` should not be called during main process.
- Can’t call setState (or forceUpdate) on an unmounted component [How to Solve]
- React Common Component Issues: Can’t perform a React state update on an unmounted component [How to Solve]
- [Solved] TypeError: Cannot read properties of undefined (reading ‘templateName’)
- MySQL timestamp set default value error Invalid default value reason and solution
- [Solved] scheduler Error: maximum number of running instances reached
- [Solved] Cannot make a static reference to the non-static field logMongoTemplate
- Three common ways of react event binding and solution can’t update during an existing state transition (such as within ‘render’)
- timer_create ,timer_settime,timer_delete
- [Solved] IDEA Unboxing of ‘stringRedisTemplate.hasKey(xx)’ may produce ‘NullPointerException’