-
-
Notifications
You must be signed in to change notification settings - Fork 529
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
Memory leaks: too many detached nodes #1190
Comments
Difficult to say what the cause is without seeing the code. Try taking a look at our troubleshooting page, specifically the "Dynamically generated anchor elements" section. https://react-tooltip.com/docs/troubleshooting#dynamically-generated-anchor-elements |
@Jayvora best I can think of is that the tooltip might be leaking nodes with the
Something like this should be good enough to test # 2: <Tooltip
...
render={({ content }) => content}
...
/> Please let us know if either test makes the detached nodes disappear. We might be able to investigate further from your findings. |
Seems to be the case with example implementation aswell, additionally can see JS event listeners flooding on every refresh or even on hovering on any tooltips.
I am suspecting possibility of some memory leak here react-tooltip/src/components/Tooltip/Tooltip.tsx Lines 458 to 637 in 143221a
|
We were using an older version of the library (5.19.0) and then upgraded to the latest (5.27.1) and reran snapshots. That solved the issue for us. My guess is that this was fixed in a recent version and y'all can probably close this issue. |
@mattathompson thanks for reporting back @Jayvora @naresh-pin can you guys confirm if it still happens for you in the latest release? |
This issue is stale because it has not seen activity in 30 days. Remove the |
There are too many detached nodes in my application, this is because of react-tooltip, if i comment it all are gone, how can i get rid of this. This i causing too many memory leaks and causing my app being laggy.
I am using v5.24.0
The text was updated successfully, but these errors were encountered: