Skip to content

fix: cleanup after a map has been removed#574

Open
dopenguin wants to merge 2 commits intonextfrom
vue3/fix-memory-leak
Open

fix: cleanup after a map has been removed#574
dopenguin wants to merge 2 commits intonextfrom
vue3/fix-memory-leak

Conversation

@dopenguin
Copy link
Member

Summary

Some parts were not properly being cleaned up leading to an explosion in RAM usage after multiple additions and removals of an additional map in snowbox. This, too, would be the case for any SPA that rerenders POLAR.

Instructions for local reproduction and review

npm run snowbox here and on next. Check the Snapshot size difference after multiple additions and removals. It should be fairly less now.
Note that there is still some overhead of about 100kb - 200kb per instance. I was not able to remove that and it may be an issue with vue directly.

@dopenguin dopenguin added this to the POLAR@3 milestone Mar 3, 2026
@dopenguin dopenguin self-assigned this Mar 3, 2026
@dopenguin dopenguin added the bug Something isn't working label Mar 3, 2026
@github-actions
Copy link

github-actions bot commented Mar 3, 2026

PR Preview Action v1.8.0

QR code for preview link

🚀 View preview at
https://Dataport.github.io/polar/pr-preview/pr-574/

Built to branch gh-pages at 2026-03-17 16:14 UTC.
Preview will be ready when the GitHub Pages deployment is complete.

@dopenguin dopenguin force-pushed the vue3/fix-memory-leak branch 5 times, most recently from 7c96842 to 2e8a936 Compare March 12, 2026 11:36
@dopenguin dopenguin force-pushed the vue3/fix-memory-leak branch from 2e8a936 to 133c2d5 Compare March 17, 2026 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant