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 just forgetting to call some cleanup method. It may also be that if you write this same code in pure JS, there will be a leak and that you cannot do anything about it.
On Wednesday, December 4, 2013 12:21:23 PM UTC-6, ak...@ualberta.net wrote: > > Hi Colin, > > <https://lh4.googleusercontent.com/-sPqHnXrVFXk/Up9xLWDPTkI/AAAAAAAAABI/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 created by, or at least related to, gwt-viz. Using > Chrome's dev tools, I can look inside these objects to verify the > connection to gwt-viz. > > > <https://lh4.googleusercontent.com/-sPqHnXrVFXk/Up9xLWDPTkI/AAAAAAAAABI/eMFgyy-yBuM/s1600/Screen+Shot+2013-12-04+at+11.04.40+AM.png> > I've trimmed the code down to a minimal test case (attached). Should you > decide to try compiling and running it, don't forget to to <inherits > name='com.google.gwt.visualization.Visualization'/> in the *.gwt.xml file. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
