I'm experiencing the same problem described in the following post from Oct. 2009.
http://groups.google.com/group/google-visualization-api/browse_thread/thread/4a15d680db43ceae/62853145be8674a5?hl=en&lnk=gst&q=leak#62853145be8674a5 Specifically, it's a memory leak when 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. I submitted a follow-up post in Nov. 2010 http://groups.google.com/group/google-visualization-api/browse_thread/thread/4a15d680db43ceae/62853145be8674a5?hl=en&lnk=gst&q=leak#62853145be8674a5 and have yet to see a resolution (or even acknowledgment) of the problem. Following is a link to an example of the problem http://threadtec.com/maps/table_leak.html The example creates a table of time-stamp values 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 over time. I see here http://groups.google.com/group/google-visualization-api/browse_thread/thread/b85fbabee8c8e79b/38ecfac6c2541788?hl=en&lnk=gst&q=leak#38ecfac6c2541788 that back in Aug. 2010 Google pushed a new release of Visualization API that fixed several bugs including "addressing the memory leak that occurred when redrawing charts." Is it possible you overlooked a similar problem with google.visualization.Table? Is there a process other than posting to this group for ensuring the issue is addressed? 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.
