Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setState errors on navigation #173

Open
oyeanuj opened this issue Apr 19, 2018 · 2 comments
Open

setState errors on navigation #173

oyeanuj opened this issue Apr 19, 2018 · 2 comments

Comments

@oyeanuj
Copy link

oyeanuj commented Apr 19, 2018

Hi @jasonkuhrt, I keep seeing these errors in the console every time I navigate or the parent component (that contains the Popover) unmounts.

warning.js:33 Warning: Can't call setState (or forceUpdate) 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 Tooltip (at LoggedInNav.js:94)
    in div (created by styled__NavSection)
    in styled__NavSection (at LoggedInNav.js:93)
    in nav (created by styled__NavBar)
    in styled__NavBar (at LoggedInNav.js:78)
    in LoggedInNav (at GeneralHeaderNav.js:126)
    in GeneralHeaderNav (created by Connect(GeneralHeaderNav))
    in Connect(GeneralHeaderNav) (at StandardPage.js:49)

Seems like it is happening within this library - thoughts on how best to fix this

Thank you!

@oyeanuj
Copy link
Author

oyeanuj commented May 28, 2018

@jasonkuhrt FYI, this is happening even with the latest versions of the library. Any ideas what might be going on?

@oyeanuj
Copy link
Author

oyeanuj commented Jun 24, 2018

@jasonkuhrt Ping - any ideas what might be happening here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant