Under special conditions, the blockStack will grow indefinitely, leading to a memory leak.

[hpxiaohao]

Version

3.5.18

Reproduction link

stackblitz.com

Steps to reproduce

• npm install && npm run dev
• Open the Chrome browser and visit the home page.
• For specific operations, please check the following video.

Video Proof: Click to view

What is expected?

Once the operation is stopped, the length of the blockStack array in runtime-core.esm-bundler.js should be reset to 0.

停止操作后，文件runtime-core.esm-bundler.js中blockStack长度应该为0.

What is actually happening?

Once the operation is stopped, the length of blockStack in runtime-core.esm-bundler.js will grow indefinitely, causing a memory leak.

---

If the line of code <div v-if="row.editConfigs[item.prop]">aaaa:</div> doesn't exist in the src/views/test-table.vuee file, there won't be any problems.

如果src/views/test-table.vue文件中没有<div v-if="row.editConfigs[item.prop]">aaaa:</div>这行代码，就不会有问题

[hpxiaohao]

This is a developer tools memory snapshot：

[edison1105]

I can reproduce this issue - the number of closeBlock calls is fewer than openBlock, causing the blockStack to ultimately not be cleared. However, when I implemented a simple Table component locally, I couldn't reproduce it, which might be related to element-plus's internal implementation.

Please first provide a reproduction that doesn't involve element-plus, or consider opening an issue in the element-plus repository first.

Edit
This one will be fixed via element-plus/element-plus#18144 (from @btea)

If there is a reproduction that does not rely on element plus, we will continue to investigate