starred/floccus

Fork 0

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

[GH-ISSUE #1957] v5.5.3 crashing at sync start #1306

New issue

Closed

opened 2026-02-25 22:39:38 +03:00 by kerem · 4 comments

kerem commented

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

Owner

Originally created by @uzzyDC on GitHub (May 14, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1957

Which version of floccus are you using?

lastest, v5.5.3

How many bookmarks do you have, roughly?

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

Sync method

Google Drive

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

Chrome and Yandex Browser

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

I have automatic syncing, when i open the browser, after a while the browser closes (crash).
Disabling the extension solved the issue.
If now I start syncing manually, still it crashes.
In Chrome, after a while, the extension was automatically reverted to [v5.4.5], which solved the issue.

In yandex it occurs in both desktop and android browser (yandex android allows extensions, reason why I'm using it. I of course also use Floccus android, just to mention it.). I tested in different computers.

Thank you

Expected Behavior

Extension working normally, not crashing the browser.

To Reproduce

Update to mentioned version of extension and run it.

Debug log provided

I have provided a debug log file

Originally created by @uzzyDC on GitHub (May 14, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1957 ### Which version of floccus are you using? lastest, v5.5.3 ### How many bookmarks do you have, roughly? 2k ### Are you using other means to sync bookmarks in parallel to floccus? No ### Sync method Google Drive ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Chrome and Yandex Browser ### 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 I have automatic syncing, when i open the browser, after a while the browser closes (crash). Disabling the extension solved the issue. If now I start syncing manually, still it crashes. In Chrome, after a while, the extension was automatically reverted to [v5.4.5], which solved the issue. In yandex it occurs in both desktop and android browser (yandex android allows extensions, reason why I'm using it. I of course also use Floccus android, just to mention it.). I tested in different computers. Thank you ### Expected Behavior Extension working normally, not crashing the browser. ### To Reproduce Update to mentioned version of extension and run it. ### Debug log provided - [ ] I have provided a debug log file

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (May 14, 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 14, 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:38 +03:00

Author

Owner

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

Hello @uzzyDC

Thank you for taking the time to give feedback by opening this issue. This problem has been reported before and is being tracked in #1947

The rollback in Chrome webstore should also affect Yandex browser if you get your extension from there. Or how are you installing floccus on there?

@marcelklehr commented on GitHub (May 14, 2025): Hello @uzzyDC Thank you for taking the time to give feedback by opening this issue. This problem has been reported before and is being tracked in #1947 The rollback in Chrome webstore should also affect Yandex browser if you get your extension from there. Or how are you installing floccus on there?

kerem commented

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

Author

Owner

@uzzyDC commented on GitHub (May 14, 2025):

Yes, it rollbacked automatically in yandex also, thank you.
If you need help in general I could try to dive into the code, maybe we should setup a call though.

Thanks

@uzzyDC commented on GitHub (May 14, 2025): Yes, it rollbacked automatically in yandex also, thank you. If you need help in general I could try to dive into the code, maybe we should setup a call though. Thanks

kerem commented

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

Author

Owner

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

Cool! I always appreciate helping hands :) Let's arrange a call via email: mklehr@gmx.net

(closing as duplicate)

@marcelklehr commented on GitHub (May 14, 2025): Cool! I always appreciate helping hands :) Let's arrange a call via email: mklehr@gmx.net (closing as duplicate)

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#1306

No description provided.

Rows
Columns