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
I've been profiling a nasty memory leak where the root cause is this as well. I'd love to have a proper way to get the createJs object properly cleaned-up.
On Thu., Jan. 30, 2020, 10:27 p.m. Julian Cerruti, ***@***.***> wrote:
I've been profiling a nasty memory leak where the root cause is this as
well. I'd love to have a proper way to get the createJs object properly
cleaned-up.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#913?email_source=notifications&email_token=AAIHPJ5MYMYUWG6DMEHLK3DRAOLARA5CNFSM4D7QHOOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKNLSVY#issuecomment-580565335>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIHPJYJP6ZHWMO3UUUMSRLRAOLARANCNFSM4D7QHOOA>
.
Thank you for the suggestion! I hadn't though of that.
Unfortunately for my case that would be very difficult to do, as this is part of a very large React application.
I think I found a solution though. I found a way to properly clean-up the Stage object from outside it by doing the following:
Hi.
I try to use Createjs in my SPA project. But in some page, I want to destroy Createjs completely.
I remove the DOM object and stage's children, event listeners.
Then there still have Detached DOM tree.
I have to manual set that stage.canvas = null; stage._eventListeners = null; ... , it can resolve this Detached DOM tree problem.
See that demo.
Want to have a right way to destroy the Stage and Createjs object completely.
Thanks.
The text was updated successfully, but these errors were encountered: