starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-26 06:35:59 +03:00

[GH-ISSUE #1946] Firefox Crash on exit #1300

New issue

Closed

opened 2026-02-25 22:39:36 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 22:39:36 +03:00

Owner

Originally created by @nunoleite on GitHub (May 6, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1946

Which version of floccus are you using?

5.5.3

How many bookmarks do you have, roughly?

1,2k

Are you using other means to sync bookmarks in parallel to floccus?

Sync method

Nextcloud Bookmarks

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

Firefox 138.0.1

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

30.0.10

Which version of Nextcloud? (if relevant)

15.1.0

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

No response

Describe the Bug

When closing Firefox, it crashes.
MozCrashReason: MOZ_CRASH(Quota manager shutdown timed out)

It was working fine with Firefox 137.x
This behavior started after upgrade Firefox to 138.0.1

Expected Behavior

Firefox should close as usually.

To Reproduce

If Floccus doesn't have any profiles to sync it seems to work fine, but if it has bookmarks to sync this behavior happens.
The synchronization is working fine while the browser is opened and while i'm browsing.
Is this because i have more than 1200 bookmarks?

Debug log provided

I have provided a debug log file

Originally created by @nunoleite on GitHub (May 6, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1946 ### Which version of floccus are you using? 5.5.3 ### How many bookmarks do you have, roughly? 1,2k ### Are you using other means to sync bookmarks in parallel to floccus? No ### Sync method Nextcloud Bookmarks ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Firefox 138.0.1 ### Which version of Nextcloud Bookmarks are you using? (if relevant) 30.0.10 ### Which version of Nextcloud? (if relevant) 15.1.0 ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug When closing Firefox, it crashes. MozCrashReason: MOZ_CRASH(Quota manager shutdown timed out) It was working fine with Firefox 137.x This behavior started after upgrade Firefox to 138.0.1 ### Expected Behavior Firefox should close as usually. ### To Reproduce If Floccus doesn't have any profiles to sync it seems to work fine, but if it has bookmarks to sync this behavior happens. The synchronization is working fine while the browser is opened and while i'm browsing. Is this because i have more than 1200 bookmarks? ### Debug log provided - [ ] I have provided a debug log file

kerem

2026-02-25 22:39:36 +03:00

closed this issue
added the
bug

priority: high
labels

kerem commented

2026-02-25 22:39:37 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (May 6, 2025):

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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general 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!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

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 Nextcloud 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.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

@github-actions[bot] commented on GitHub (May 6, 2025): Hello :wave: 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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general 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! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! 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 Nextcloud 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. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers :blue_heart:

kerem commented

2026-02-25 22:39:37 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 7, 2025):

Hello @nunoleite

Thank you for giving feedback by opening this issue!

It was working fine with Firefox 137.x
This behavior started after upgrade Firefox to 138.0.1

It could also be that the update to floccus v5.5.3 caused this. If the firefox update really caused this, I think it's likely an issue in firefox. I will investigate.

@marcelklehr commented on GitHub (May 7, 2025): Hello @nunoleite Thank you for giving feedback by opening this issue! > It was working fine with Firefox 137.x > This behavior started after upgrade Firefox to 138.0.1 It could also be that the update to floccus v5.5.3 caused this. If the firefox update really caused this, I think it's likely an issue in firefox. I will investigate.

kerem commented

2026-02-25 22:39:37 +03:00

Author

Owner

@nunoleite commented on GitHub (May 15, 2025):

I have updated Firefox to version 138.0.3 and Floccus to 5.5.3.1, and it seems to be solved.

@nunoleite commented on GitHub (May 15, 2025): I have updated Firefox to version 138.0.3 and Floccus to 5.5.3.1, and it seems to be solved.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/floccus#1300

No description provided.

Rows
Columns