It appears there is a memory leak in the Visualization API associated with redrawing an instance of the Table Visualization component. In my case, I'm redrawing the table to reflect additions/deletions that occur over time in response to user inputs.
Following is a link to an simple example of the problem http://threadtec.com/maps/table_leak.html The example creates a table of time-stamp values (1 per row) and then cycles through the table (updating 1 entry every 2 seconds) changing one of the time-stamp values from its old value to the current time. It's easy to observe how the memory usage of the browser (Firefox 3.6.15 in my case) grows steadily time. Kevin H. -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
