-
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
Memory leak while generating a lot of server side graphs #30
Comments
Hey @varsha2409 I would check to see if something is holding on to the Often times when you see these kinds of issues it is due to a large object (like |
Hey @sedouard did you find anything? |
@varsha2409 are you able to copy/paste the full context you're running this library in? I'm interested in seeing how it is repeatedly called. I suspect you are holding on to a references and thats why you're experiencing a leak. |
@varsha2409 I've got a PR open, #43, that may address your issues--any chance you could give my fork a go to see if it helps you at all? |
Hey guys, I'm still having trouble with this. Calling destroy is not removing the instance of the chartNode. I am using Any insight?
|
@tscritch I think u want to be destroying the chart instance in ur finally block? |
When running openITCOCKPIT for a long time the nodejs server running ChartRenderer.js consumes more and more memory. This should fix it. See vmpowerio/chartjs-node#30
Hi,
I am generating a lot of images on server side. During the process, Node is consuming a lot of memory (~ 1.5 GB).
I am calling chartNode.destroy(), still memory is not getting released.
Does anyone knows, where else there could be a memory leak?
PFB my code:
The text was updated successfully, but these errors were encountered: