-
-
Notifications
You must be signed in to change notification settings - Fork 404
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 leak with bokeh serve and datashader #2111
Comments
Apologies I never responded here. I haven't investigated but I have a few thoughts on what might be hanging around, stream callbacks being the most likely candidate. I think this is a priority to fix before 1.10.0. |
Great to hear. Looking forward to a potential fix. |
Just following up on this, I am having the same problems. I made a mre which has the same bug (but smaller footprint as I generate random data rather than read in such a large amount of data).
Served with |
Thank you, I recently merged a change into bokeh that will let us clean up after a session is killed more easily. I'll use your example to check whether that is enough to address these issues. |
Thank you both for your examples, after a marathon debugging session I've finally addressed the issue. |
I am facing the same memory leak problem with panel serve using holoviews with datashading. Should I open a new issue for it? |
Sure, but please include detailed information about your environment (versions of packages, how installed, platform, etc) and how to reproduce (e.g. one of the scripts above). |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
I believe I am encountering a memory leak when using datashader in combination with a 'bokeh serve' style application.
Here is a simplified case that will reproduce the issue:
Add this to a folder
test
and run:then try opening up a tab or two. Close the tabs and wait a minute or so for the sessions to be destroyed.
Afterward it appears that memory is not reclaimed.
Though it is hard to do with non-datashaded lines if you run the same experiment (with fewer datapoints) and a normal overlay, it appears the memory is reclaimed. I tried to dig into the persistent objects in the on_session_destroyed hook, and it seems at least the datashader object is not garbage collected when the session is destroyed. Not sure what else might be hanging around.
Am I missing something in the implementation?
The text was updated successfully, but these errors were encountered: