--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To post to this group, send email to google-visua...@googlegroups.com.
To unsubscribe from this group, send email to google-visualizati...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-visualization-api?hl=en.
Any fixes/work around for this are in ?I am facing similar issue.
On Sunday, November 28, 2010 2:45:07 PM UTC+5:30, ChartMan wrote:
Thanks for reporting.ChartMan
On Fri, Nov 26, 2010 at 1:14 AM, kjh <hea...@verizon.net> wrote:
I'm experiencing the same problem described in the following post:
http://groups.google.com/group/google-visualization-api/browse_thread/thread/20643ff2c0370f02/7a5b3ff030b3fa6b?hl=en&lnk=gst&q=memory+leak#7a5b3ff030b3fa6b
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.
In the few responses to the original post cited above, no resolution
(or even acknowledgment) of the problem was offered.
It's not difficult to reproduce. Create a table, change an element
and redraw it and watch the memory leak.
Any updates on this?
--
You received this message because you are subscribed to the Google Groups "Google Visualization API" group.
To post to this group, send email to google-visua...@googlegroups.com.
To unsubscribe from this group, send email to google-visualization-api+unsub...@googlegroups.com.