Skip to content

Detached elements casued by getting computed value in ref function #13209

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.

Sign up for GitHub

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

Jump to bottom
Closed
makedopamine opened this issue Apr 16, 2025 · 0 comments · Fixed by #13210
Closed

Detached elements casued by getting computed value in ref function #13209

makedopamine opened this issue Apr 16, 2025 · 0 comments · Fixed by #13210
Labels
❗ p4-important Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf.

Comments

@makedopamine
Copy link
Contributor

makedopamine commented Apr 16, 2025 •
edited
Loading

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
This was referenced Apr 16, 2025
Merged
Closed
@edison1105 edison1105 added the ❗ p4-important Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf. label Apr 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
❗ p4-important Priority 4: this fixes bugs that violate documented behavior, or significantly improves perf.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(runtime-core): stop tracking deps in setRef during unmount makedopamine/core
2 participants
@edison1105 @makedopamine