Memory leak while generating a lot of server side graphs about chartjs-node

[moberemk]

@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?

[sedouard]

Hey @varsha2409 I would check to see if something is holding on to the chartNode reference.

Often times when you see these kinds of issues it is due to a large object (like chartNode which contains a virtual DOM) that sits high in scope and never gets dereferenced for garbage collection.

[varsha2409]

Hey @sedouard did you find anything?
I analysed the heap dump, there are many ChartElement, Chart.Controller and other Chart related objects.
I even did a force GC after every chart is created, these elements were still present.

[sedouard]

@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.

[tscritch]

Hey guys,

I'm still having trouble with this. Calling destroy is not removing the instance of the chartNode.

I am using v1.7.1

Any insight?

return new Promise(function (resolve, reject) {
  var chartNode = new Chart(_options.width, _options.height)

  var options = {...}

  chartNode.drawChart(options)
        .then(() => {
          if (_options.base64) {
            // if base64 was in the query then return base64 data
            return chartNode.getImageDataUrl(_options.type)
          } else {
            // else return the image buffer
            return chartNode.getImageBuffer(_options.type)
            }
        })
        .then(image => {
          resolve(image)
        })
        .finally(() => {
          chart.destroy()
        })
        .catch(error => {
          reject(error)
        })
    })

[jacktuck]

@tscritch I think u want to be destroying the chart instance in ur finally block? chartNode.destroy ?