Issue 529 in gwt-google-apis: Removing PieChart from parent widget leaves elements in detached DOM tree

[gwt-goo...@googlecode.com]

Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 529 by ak...@ualberta.net: Removing PieChart from parent widget
leaves elements in detached DOM tree
http://code.google.com/p/gwt-google-apis/issues/detail?id=529

Found in Release: 1.1.1

Platform information: OS X 10.9, Chrome 31.0.1650.57, GWT 2.5.1. Unknown
if this problem exists on other platforms.

After adding a PieChart to a widget (for example, a VerticalPanel or as a
new Tab in a TabPanel) and then removing the PieChart (using
HasWidgets.remove(widget) or IndexedPanel.remove(index)), the PieChart no
longer appears within the enclosing widget as expected.

However, when I check Chrome Dev Tools Containment view, I can see that
elements for the PieChart remain behind in a detached DOM tree, instead of
being garbage collected.

No workaround at present.

No relevant Google Group posts, but you can check out a sample project that
demonstrates this behavior here: https://github.com/akydd/GWT-experiments.

The PieChart add/remove functionality is in this presenter:
https://github.com/akydd/GWT-experiments/blob/master/src/main/java/demo/client/presenter/Presenter2.java

Attachments:
Screen Shot 2013-11-20 at 4.49.20 PM.png 126 KB

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[gwt-goo...@googlecode.com]

Comment #1 on issue 529 by ak...@ualberta.net: Removing PieChart from

parent widget leaves elements in detached DOM tree
http://code.google.com/p/gwt-google-apis/issues/detail?id=529

Not sure if this issue exists in Firefox, but in 25.0.1 for OS and GWT as
above, about:memory shows 7,761,272 bytes in orphan-nodes with the code on
Github, after adding and removing the PieChart.

When a Label is added/removed, the orphan-node byte count is only 3,392 B.