Skip to content
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

Maxiumum call stack happens on HMR with :ref="setElement" and editing that component #6930

Closed
sapphi-red opened this issue Oct 23, 2022 · 0 comments · Fixed by #6936
Closed
Labels
🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. 🐞 bug Something isn't working scope: hmr

Comments

@sapphi-red
Copy link
Contributor

Vue version

3.2.41

Link to minimal reproduction

https://stackblitz.com/edit/vitejs-vite-qrfyaa?file=src%2FApp.vue,src%2FFoo.vue

Steps to reproduce

  1. Open reproduction
  2. Change const count = ref(5); in Foo.vue to const count = ref(56);
  3. The warning happens

This does not happen if <Foo ref="component" /> is used instead of <Foo :ref="changeRef" /> in App.vue.

What is expected?

No warning happens.

What is actually happening?

The following error happens.

vue.js?v=f54006de:1274 [Vue warn]: Maximum recursive updates exceeded in component . This means you have a reactive effect that is mutating its own dependencies and thus recursively triggering itself. Possible sources include component template, render function, updated hook or watcher source function.

System Info

No response

Any additional comments?

Original issue: vitejs/vite#9713

@edison1105 edison1105 added 🐞 bug Something isn't working scope: hmr labels Oct 23, 2022
@sodatea sodatea added the 🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. label Mar 27, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Jun 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
🔨 p3-minor-bug Priority 3: this fixes a bug, but is an edge case that only affects very specific usage. 🐞 bug Something isn't working scope: hmr
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants