Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible Firefox memory leak #1593

Closed
1 task
balporig opened this issue May 8, 2024 · 5 comments
Closed
1 task

Possible Firefox memory leak #1593

balporig opened this issue May 8, 2024 · 5 comments
Labels
Projects

Comments

@balporig
Copy link

balporig commented May 8, 2024

Which version of floccus are you using?

5.1.0

Sync method

WebDAV

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Firefox 125.0.3

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

No response

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

Setup

75k bookmarks spread across 8 non-nested profiles synced between several Firefox and Chromium based browsers on different platforms with auto-sync disabled

Issue

When opening Firefox for the first time there is huge memory spike up to 40 GB. Each time you reopen the browser there is significant spike, that takes few minutes to reach it's peak and disappears after several minutes. With auto-sync disabled there shouldn't be any background processing on startup. The issue is not present in Chromium based browsers

Expected Behavior

There shouldn't be any noticeable memory usage on startup with auto-sync disabled

To Reproduce

You need couple of profiles each with few thousand bookmarks, the more profiles with more bookmarks, the larger the memory spike

Debug log provided

  • I have provided a debug log file
@balporig balporig added the bug label May 8, 2024
@github-actions github-actions bot added this to Backlog in Floccus May 8, 2024
Copy link

github-actions bot commented May 8, 2024

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus and have been maintaining it ever since.
I currently work for Nextcloud which leaves me with less time for side projects like this one
than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

I look forward to working with you on this issue
Cheers 💙

@marcelklehr
Copy link
Member

75k bookmarks, huh?

I know exactly which code triggers this :D :S and it's hard to circumvent 🤔

@marcelklehr marcelklehr moved this from Backlog to To Do: Bugs in Floccus May 8, 2024
@balporig
Copy link
Author

balporig commented May 8, 2024

Yep, 10 years worth of research :)

Interesting, can you point to the code to have a look?

Looks like #1548 is non issue anymore as long you keep each profile under 5 MB

Floccus automation moved this from To Do: Bugs to Done May 9, 2024
@marcelklehr
Copy link
Member

Interesting, can you point to the code to have a look?

You can see it in the fixing commit

@marcelklehr
Copy link
Member

Looks like #1548 is non issue anymore as long you keep each profile under 5 MB

Interesting

marcelklehr added a commit that referenced this issue May 9, 2024
if we can help it

fixes #1593

Signed-off-by: Marcel Klehr <mklehr@gmx.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

2 participants