Open FelixNumworks opened 1 month ago
If this has to do with anything, it would be with how Vue manages the memory, not with Quasar UI itself, but will investigate. Can you reproduce with anything else other than a QInput though?
Yes the QInput part isn't relevant. I just used it in my example for simplicity. In reality I use a custom component with a more complex model.
If it can help you, I have hundreds of these large __vnode
and transition
items.
What happened?
When I update the model of the default slot of
q-extension-item
, memory is leaked if this slot is not filled with aq-item-section
This leaks memory when
myString
is updatedThis works well when
myString
is updatedWhat did you expect to happen?
No memory leak
Reproduction URL
https://stackblitz.com/edit/quasarframework-ygojpg?file=src%2Fpages%2FIndexPage.vue
How to reproduce?
I didn't manage to see the memory go up directly on stackblitz, but it might be due to the fact that the code is executed in an iframe
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
Components (quasar)
Platforms/Browsers
Chrome
Quasar info output
Relevant log output
No response
Additional context
No response