So, in our preliminary analysis we found out bunch of things:
1. Some charting libraries do not discard a infinitely growing time series data. For example, if you are only displaying 20 data points in graph, holding older data points do not make sense. Obviously this had nothing to do limitation of webkit platform but library under question being sloppy.
2. In few cases, we noticed all those charting tool tips and popovers in case of time series data cause bunch of leaks. Disabling tooltips etc helped reducing memory growth, but did not completely eliminate it.
3. There are indeed some browser bugs, it could be what `/u/wbkang ` is saying or something else. I didn't spend lot of time investigating. Here is a sample app I put together that reproduces the leak in Chrome - https://github.com/gnufied/tryc3 you got to let it run for awhile though (like > 20 mins) .
Not sure if you will see my message, but we ended up using chart.js via Qtwebkit bridge. We got rid of bunch of fluff like labels etc though (and reduced how often charts are refreshed). Even though chart.js is canvas based, its performance is not optimal if you let it run for > 40 mins or so.
