You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Developers should get a information that Element.empty fires only dispose (against my first guess of destroy) on all children. Maybe a advise like Call myElement.getChildren().destroy() to prepare all items for garbage collection should help, too.
I didn't know it before I have took a look into the code and have now some troubles resulting out this.
Also possible: since nobody should know it without looking in the code, I would recommend to call destroy instead of dispose like @kentaromiura it did in his pull request #2351 (4c68d39) to prevent a memory leak. But the hint mentioned above should also do it.
The text was updated successfully, but these errors were encountered:
Developers should get a information that
Element.empty
fires onlydispose
(against my first guess ofdestroy
) on all children. Maybe a advise likeCall myElement.getChildren().destroy() to prepare all items for garbage collection
should help, too.I didn't know it before I have took a look into the code and have now some troubles resulting out this.
Also possible: since nobody should know it without looking in the code, I would recommend to call
destroy
instead ofdispose
like @kentaromiura it did in his pull request #2351 (4c68d39) to prevent a memory leak. But the hint mentioned above should also do it.The text was updated successfully, but these errors were encountered: