Noticed that containerGroups are no longer destroyed and this can (and in my case did) cause memleaks. Solver is adding the one line that was present in previous versions.
destroy: function () { this.traverse(function(object){ object._destroy(); }) this.rootGroup._destroy(); }
Noticed that containerGroups are no longer destroyed and this can (and in my case did) cause memleaks. Solver is adding the one line that was present in previous versions.
destroy: function () { this.traverse(function(object){ object._destroy(); }) this.rootGroup._destroy(); }