Open axetroy opened 2 months ago
I found that after each instantiation, there would be Selecto instances that were not destroyed and kept occupying memory.
I have such a scenario, which often needs to be created and then destroyed, which brings memory leaks to my application.
Here are the steps I took to reproduce:
Snapshot 1:
Snapshot 2:
Diff snapshot:
Theoretically, when the page is switched, the Selecto object should be destroyed and recycled by GC, but in fact it is not.
Selecto@295827 Still accessible
Selecto@295827
Environments
Description
I found that after each instantiation, there would be Selecto instances that were not destroyed and kept occupying memory.
I have such a scenario, which often needs to be created and then destroyed, which brings memory leaks to my application.
Here are the steps I took to reproduce:
Snapshot 1:
Snapshot 2:
Diff snapshot:
Theoretically, when the page is switched, the Selecto object should be destroyed and recycled by GC, but in fact it is not.
Selecto@295827
Still accessible