Skip to content

Detached elements due to cached static vnodes #13211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
makedopamine opened this issue Apr 16, 2025 · 2 comments · May be fixed by #13215
Open

Detached elements due to cached static vnodes #13211

makedopamine opened this issue Apr 16, 2025 · 2 comments · May be fixed by #13215
Labels
❗ p4-important Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf. has workaround A workaround has been found to avoid the problem

Comments

@makedopamine
Copy link
Contributor

makedopamine commented Apr 16, 2025

Vue version

3.5.13

Link to minimal reproduction

Playground

Steps to reproduce

  1. Open DevTools and navigate to memory tab
  2. Click "Hide" button
  3. Take a heap snapshot and filter using "detached <h1>"

What is expected?

Detached <h1> shouldn't show up in the memory profile.

What is actually happening?

Detached <h1> shows up in the memory profile.

System Info

Chrome 135.0.7049.85

Any additional comments?

No response

@edison1105
Copy link
Member

a workaround

plugins: [vue({ template: { compilerOptions: { hoistStatic: false } } })],

@edison1105 edison1105 added has workaround A workaround has been found to avoid the problem 🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. and removed 🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. labels Apr 16, 2025
@makedopamine
Copy link
Contributor Author

The workaround works well. Feel free to close this ticket if you want.

@edison1105 edison1105 added the ❗ p4-important Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf. label Apr 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
❗ p4-important Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf. has workaround A workaround has been found to avoid the problem
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants