support for dynamically changing data about google-visualization-issues HOT 10 CLOSED

I believe that you should be able to upload just the new data and then use
DataTable.addRows() to add the new rows to the datatable.

Then have the ATL draw the new table.  (this will cause a flash)...but you can do a
double buffering scheme to get rid of that.

I agree with Peter.   I have a page that is doing a 1hz update to 4 Gauges on a page,
and it leaks memory.   The browser consumed 1.5gig of RAM in 4 hours.

Todd

agree .. I need this redraw to be adressed .. it sucks

Is there any workaround for this? 

I am also looking for this solution.

Same  here, looking for a good solution on this. It's rather strange no one is picking
up on this or even gives a comment on it :)

Can someone from Google look into this.  We are planning to use these visualizations
for a dashboard application, and if there's a memory leak we will run into problems.

With reasonable amounts of data, the visualization should be efficient for redrawing
themselves quite rapidly. Some of them also adjust to the new data only and does not
require to draw everything from scratch.  Not sure which visualization you are using
as this was not specified in this thread.

Charts will leak memory if you recreate the objects every time, but if you update the
 same Options and DataTable objects and then call the draw(data) or draw(data,options)
method in the chart it will not leak.
To be on the safe side you can assume that gwt-visualization objects will not be garbage
collected. So reuse them.