mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #836] Memory leak in floccus #534
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#534
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Whissi on GitHub (Feb 16, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/836
Describe the bug
I suspect there is a memory leak in floccus.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Memory usage of floccus add-on should stay the same (something between 20-40MB; it's higher during sync but should free up memory afterwards). But after some hours, floccus has reached 400MB. I accidentally left browser running during weekend and on Monday, Browser Task Manager showed more than 3GB RAM usage just for floccus extension. Whole browser was sluggish (not even another website was loaded). After disabling extension, browser recovered.
Desktop
@marcelklehr commented on GitHub (Feb 18, 2021):
Thanks for reporting, I'll look into this!
@marcelklehr commented on GitHub (Feb 18, 2021):
This should be fixed in v4.4.9. Microsoft has been sitting on the latest release for 10 days now, hough 🙀
@github-actions[bot] commented on GitHub (Mar 21, 2023):
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.