fix: resolve critical memory leak in VPivottableUi component (#270) #285
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Fixes #270 - Critical memory leak causing memory to increase from 50MB to 881MB after 1000 refreshes.
Problem
Solution
deep: truefrom watch, useimmediate: trueinsteadcomputedPivotData withshallowRefto reuse instancesonUnmountedlifecycle hookResults
Testing
Breaking Changes
None - This is a internal optimization that doesn't affect the API.
Related Issue
Closes #270