Home forums Report Bugs Memory Leak

This topic contains 3 replies, has 4 voices, and was last updated by  Bivek Singh 12 months ago.

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
  • #14828


    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.
    Our application is a single page JSF application. Is there any javascript call or other solution that can free up memory used by previously rendered canvasjs charts in this case?

    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 Debnath
    Team CanvasJS



    Sanjoy–Having the same issue as Alex, what was the solution to this problem?


    Bivek Singh


    We introduced a new destroy method in v1.9.8.1 which solves this problem. For more details please take a look at this page.

    Bivek Singh,
    Team CanvasJS

Viewing 4 posts - 1 through 4 (of 4 total)

You must be logged in to reply to this topic.