-
Notifications
You must be signed in to change notification settings - Fork 52
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
Performance issues with a lot of curves #68
Comments
Hi @benb545 did you fix this or find an alternative? |
@mvrozanti nope still having it. What are you experiencing? |
The same, pretty much. I tried using canvas as renderer to see if it made a difference performance-wise and it crashed, I probably did something wrong. I wouldn't mind some examples on how to set it up. I have to draw 30k curves every 2 seconds or so |
I see. I've tried canvas too with the same issue. |
@benb545 have you tried adding and removing the curves without animating them? That would help us narrow down the possible cause of the possible memory leak. |
When having a lot of curves animating, by adding/removing them from the map every time, the javascript heap size always increases along with the amount of nodes in the DOM.
I am not sure why, but it's definitely not in how I handle the curves. If I remove all layers in the map, the heap size/amount of nodes does not decrease, it's something in the library and I am unsure why.
The text was updated successfully, but these errors were encountered: