Number of GoogleChartComponent's are building up on every page with charts reload

[peterlitvak]

I'm using version 4 of the ng2-google-charts and noticed that on every page reload the number of the GoogleChartComponent' s is growing proportionally to the number of charts on the page.
In the memory profiler it shows the the retainer is _this in system
Is there a special way I need to cleanup the components?
I've seen an issue where people were asking about cleanly destroying the component but I didn't see actual suggestion to do so.

[gmazzamuto]

I'm not sure I fully understand your problem. Are you refreshing the page like in a normal browser refresh? Or are you dynamically redrawing your page? That the number of GoogleChartComponent is equal to the number of charts in the page is expected.

[peterlitvak]

There are routes that load our dashboard components.
The dashboard component contains multiple google-chart components in it.
When one dashboard is loaded and another is destroyed the GoogleChartComponent's from a previous dashboard are still held in memory.

[gmazzamuto]

Unfortunately this is not an easy thing to investigate, and I suspect that the cause of this is mostly to be attributed to the underlying Google Charts library rather than to this package. There are many reports of memory leaks indeed, which apparently are even made worse by using a dashboard:

• Memory leak in all most chart types google/google-visualization-issues#1996
• Bug: Very High Memory usage on all chart types and made worse by using a dashboard. google/google-visualization-issues#1225

However I have made these changes that do seem to have some minor effect on your problem. Can you please try them out? (see above). Also, I suggest that you update to the latest version of this package, which in turn uses a more recent version of Google Charts (breaking changes should be minimal).