vue
vue copied to clipboard
Memory leak when using functional components in Vue 2.7.14
Vue version
2.7.14
Link to minimal reproduction
https://github.com/diegoexplicatis/vue-2-functional-component-memory-leak
Steps to reproduce
See README.md of reproduction link
Project setup
npm install
Run project
npm run serve
How to reproduct memory leak
-
Open base url of project (printed in console)
-
Click on "Go to Test Component"
-
Click on Home
-
Open developer tools and take a heap snapshot
-
Filter for "Objects retained by detached DOM nodes"
-
See there are detached elements, e.g. a paragraph element with id = testParagraph.
-
Manually trigger garbage collection
-
Take another heap snapshot and filter for "Object retained by detached DOM nodes" again
-
See that e.g. the paragrpah is still being retained => paragraph element has leaked (it is detached from the DOM but is not being garbage collected)
-
Go to FunctionalComponent.vue to line 4 and change the parameter for functional to "false"
-
Redo steps 1 - 8
-
See that there are not detached elements (even without manually garbage collecting) => all elements have been properly garbage collected
Repeatedly executing steps 2. and 3. leads to an increasing memory usage i.e. repeating the steps five times leads to five detached paragraph elements that do not get garbage collected!
What is expected?
I would expect that after executing steps 1-8, e.g. the paragraph element is not being retained anymore and has been garbage collected independent of the value for the functional parameter in FunctionComponent.vue
What is actually happening?
Instead the paragraph element is being retained when using functional: true
and does not get garbage collected.
System Info
System:
OS: Windows 10 10.0.19045
CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
Memory: 6.27 GB / 23.86 GB
Binaries:
Node: 18.15.0 - C:\Program Files\nodejs\node.EXE
npm: 9.5.0 - C:\Program Files\nodejs\npm.CMD
Browsers:
Edge: Chromium (128.0.2739.79)
Internet Explorer: 11.0.19041.4355
npmPackages:
vue: ^2.7.14 => 2.7.16
Any additional comments?
No response