You are correct - the same leak appears when adding and then removing a
chart using the Google Chart API directly. It is not a GWT specific issue.
The Google Chart API team is already aware of memory leak
issueshttp://code.google.com/p/google-visualization-api-issues/issues/detail?id=1313
.
Hi Colin,
https://lh4.googleusercontent.com/-sPqHnXrVFXk/Up9xLWDPTkI/ABI/eMFgyy-yBuM/s1600/Screen+Shot+2013-12-04+at+11.04.40+AM.png
Thanks for replying so quickly. I've tried compiling with
-Dgwt.style=PRETTY and even DETAILED, but the short variable names remain
for DOM objects
Good to know - that makes it seem rather likely that this leak is entirely
within the core visualization code, rather than anything specific to gwt. I
would look at plain JS examples of how to use the library, and make sure
that a step isn't being missed either by virtue of writing in GWT or by
I posted this to Stackoverflow http://stackoverflow.com/q/20129862/770519and
to the gwt-vizualization team as a possible
bug http://code.google.com/p/gwt-google-apis/issues/detail?id=529, but I
have not received any replies from either post. Perhaps someone here has
some insight into what is
Can you try compiling in PRETTY? This will make the retaining tree graph in
chrome's inspector easier to tell where things are coming from and what is
tracking them. But at a glance, something registered something with
google.visualization, and didn't unregister it. Knowing what gD, iv, and fv
