selecto
selecto copied to clipboard
Memory leak
Environments
- Framework name: none
- Framework version: none
- Component name: none
- Component version:none
- Testable Address(optional):none
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:
- Open story book welcome page and open devTool
- Trigger GC in devTool
- Take memory snapshot 1
- Open another page in storage book (eg. Select in real time)
- Go back to story book welcome page
- Trigger GC in devTool
- Take memory snapshot 2
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