inconsistency during unmount
See original GitHub issueHey,
there is an inconsistency during componentDidUnmount
, most of the time this.nextBase
is populated but sometimes this.base
will and this.nextBase
is null
don’t have a repro yet, it happens in many places in my app and in different components
could be the cause of this is similar as the one that prevented me from using any version from beta19+
will provide a repro if I manage to figure out how to break it outside of my app
Issue Analytics
- State:
- Created 7 years ago
- Comments:15 (15 by maintainers)
Top Results From Across the Web
Archived | Resolving problems unmounting partitions
When the system won't let you unmount a device because that device is busy, examining every process on the system is both irritating...
Read more >Micro SD Card Keeps Unmounting: 5 Methods to Fix the Issue
If your SD card keeps unmounting, there could be an underlying problem. This article will show you how to stop your SD card...
Read more >Network connections dropping or volumes unmounting
If Finder/Explorer is reporting the volume is unmounted after the workstation was idle, one of the most frequent causes is the workstation's ......
Read more >82037 – mount(8)/unmount(8)/fsck(8) mount point specification ...
Bug 82037 - mount(8)/unmount(8)/fsck(8) mount point specification inconsistency. ... and '/b' is specified as a mountpoint in /etc/fstab, an attempt to do ...
Read more >ReactJS componentWillUnmount not called on route change
componentWillUnmount function is called when a component no longer required, if you change the route and the component is required on ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
your comment gave me an idea, made a repro 😃
http://jsfiddle.net/pstma6fj/
I modified your example to only log the error case, and verified that with the fix in place (
5.5.0
), the error case is never triggered: http://jsfiddle.net/developit/b0ymwy6c/