mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #334] memory leak on firefox while using webdav #280
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#280
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 @GoogleBeEvil on GitHub (Jul 22, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/334
Step to reproduce:
1.set usename and password for floccus
2.sync all local bookmarks to webdav with check "Speed up synchronization"
these 2 steps works well and no memory leak.
3.delete all local bookmarks and then try sync back bookmarks from webdav (checked Trigger sync from scratch,also check Speed up synchronization) .memory usage will grow till fiiefox gets stucked 16GBram,and firefox use 12GB.
btw:4000 bookmarks in my local folder,maybe the number of bookmarks lead this , one more thing i use debian testing x64,firefox 68.0.1
@GoogleBeEvil commented on GitHub (Jul 22, 2019):
and for firefox get stucked,the bookmarks fails to be sync back
@marcelklehr commented on GitHub (Jul 23, 2019):
Does this also happen when disabling speedup?
@GoogleBeEvil commented on GitHub (Jul 23, 2019):
yes ,so this isnt speedup matter.just connect to webdav even you nnednt click sync ,just export and delete all your bookmarks,then restore bookmark by import , ,ram grows
@marcelklehr commented on GitHub (Jul 31, 2019):
In this case I dare say the problem is not with floccus, as floccus doesn't interfere with normal browser imports.
@marcelklehr commented on GitHub (Aug 2, 2019):
If the browser is not the problem, this migt be fixes in the latest beta
@GoogleBeEvil commented on GitHub (Aug 4, 2019):
i dont know which side lead this ,but once floccus installed ,it appears. sync function is ok,but with webdav login in , import bookmark.json will memory leak.need to do more test.is there any log file that floccus created in firefox profile folder?
@marcelklehr commented on GitHub (Aug 4, 2019):
I recommend creating a new profile, installing floccus (preferably the beta version linked above, so that you have the latest code). Then you can follow the steps for debugging outlined here
@GoogleBeEvil commented on GitHub (Aug 4, 2019):
have tested the beta version with newly created profile,same result.
log file,seems nothing wrong
http://paste.debian.net/1094337/
@marcelklehr commented on GitHub (Aug 4, 2019):
This sync run caused a memory leak?! That's odd.
@GoogleBeEvil commented on GitHub (Aug 5, 2019):
actully， I dont think sync cause memory leak ,but the "import bookmark.json from local file" function conflict with " webdav matters ".Only sync bookmark would not cause memoryleak,and if i delete my webdav account from floccus,then import boookmark.json,it wont memory leak.
Maybe the webdav service provider or ISP，whatever u call it，conflict with floccus，though it is hardly possible。
btw：i use jianguoyun.com as webdav ftp. I should try another webdav provider ,maybe. two more things:1.Both linux and windows are affected. 2.i dont test on chrome
@marcelklehr commented on GitHub (Aug 10, 2019):
Thanks for the details! I think I know what the problem is.
@marcelklehr commented on GitHub (Aug 10, 2019):
Could you try the new beta and report back?
@GoogleBeEvil commented on GitHub (Aug 12, 2019):
seems fixed the problem ，but still have some issue,it get stucked and no response while testing ,though only just one time ,maybe it's the network problem.need further test
@marcelklehr commented on GitHub (Aug 19, 2019):
Any news?
@GoogleBeEvil commented on GitHub (Aug 20, 2019):
just close this . it do have some other issues,but no related with this memory leak issue.actually ,i forget what the "other issues" is...maybe is the "merge local and webdav bookmarks and sync back",after i read the wiki and make sure how to reproduce it ,i will open new issues
@GoogleBeEvil commented on GitHub (Aug 20, 2019):
BTW, the memory leak seems solved
@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.