Home › forums › Report Bugs › Memory Leak
Tagged: memory leak
This topic contains 5 replies, has 6 voices, and was last updated by Priyanka M S 6 months, 1 week ago.
See this jsfiddle example http://jsfiddle.net/xhoycvsn/21/
1) In this example when you click the ‘run’ button and then ‘reload’ and ‘run’ multiple times the browser memory increases and never releases.
2) Our charts are very dynamic, the user can run a report with any number of charts and then go back and run a different report with completely different charts.
Unfortunately since we are using JSF and a single page the dom does not change. How can we free the memory from previously rendered canvasjs charts?
3) We understand the update() functionality which appends data to existing charts json (which we are already using in other cases), but that solution is not applicable in case this due the reason described in above points.
We have replied to you and your team via mail.
Sanjoy–Having the same issue as Alex, what was the solution to this problem?
We introduced a new destroy method in v220.127.116.11 which solves this problem. For more details please take a look at this page.
We are facing the same issue, we are using destroy method also, but still increasing memory
we have a dashboard page, it will show dashboard for each level, while switch between levels memory is increasing continuously.
in our application while switching between level we first destroy every existing charts using destroy method, then create new dashboard with charts, but still increasing memory
I recommend you to use the latest version of CanvasJS – v2.2.
If you are still facing the issue in the latest version, kindly provide the browser details and share a jsfiddle reproducing the issue you are facing so that we can understand your scenario better and help you out.
Priyanka M S
You must be logged in to reply to this topic.