q-tree performance issue #17941
Description
What happened?
Expanding or ticking q-tree component's parent node with 5939 children freezes UI and takes considerable time to expand or tick all children nodes. Using q-tree component increases memory by ~400mb.
What did you expect to happen?
Ticking or expanding tree's parent node should be fast.
Reproduction URL
How to reproduce?
- Go to provided reproduction URL
- Click 'Select all' checkbox
Flavour
Quasar CLI with Vite (@quasar/cli | @quasar/app-vite)
Areas
Components (quasar)
Platforms/Browsers
No response
Quasar info output
Operating System - Windows_NT(10.0.26100) - win32/x64
NodeJs - 22.14.0
Global packages
NPM - 9.7.2
yarn - Not installed
pnpm - Not installed
bun - Not installed
@quasar/cli - 2.5.0
@quasar/icongenie - Not installed
cordova - Not installed
Important local packages
quasar - 2.18.1 -- Build high-performance VueJS user interfaces (SPA, PWA, SSR, Mobile and Desktop) in record time
@quasar/app-vite - 2.2.0 -- Quasar Framework App CLI with Vite
@quasar/extras - 1.16.17 -- Quasar Framework fonts, icons and animations
eslint-plugin-quasar - Not installed
vue - 3.5.13 -- The progressive JavaScript framework for building modern web UI.
vue-router - 4.5.0
pinia - Not installed
vite - 6.2.3 -- Native-ESM powered web dev build tool
vite-plugin-checker - Not installed
eslint - 9.23.0 -- An AST-based pattern checker for JavaScript.
esbuild - 0.25.1 -- An extremely fast JavaScript and CSS bundler and minifier.
typescript - Not installed
workbox-build - Not installed
register-service-worker - Not installed
electron - Not installed
@electron/packager - Not installed
electron-builder - Not installed
@capacitor/core - Not installed
@capacitor/cli - Not installed
@capacitor/android - Not installed
@capacitor/ios - Not installed
Quasar App Extensions
*None installed*Relevant log output
Additional context
No response