starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 14:16:12 +03:00

[GH-ISSUE #2180] Chrome IndexedDB grows indefinitely #1464

New issue

Closed

opened 2026-02-25 22:40:05 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 22:40:05 +03:00

Owner

Originally created by @gdm257 on GitHub (Feb 22, 2026).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2180

Which version of floccus are you using?

5.8.6

How many bookmarks do you have, roughly?

about 30k

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

also sync via Google account

Sync method

Git

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

Cent Browser 5.2.1168.83 (Chromium 134.0.6998.136)

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

Floccus's IndexedDB took large disk usage in several months. It is 221.9 GiB and grows indefinitely from every sync.

#1913 #1915 have similar problems.

# Apparent size: 221.9 GiB Items: 58327

demo@windows10 ~/scoop/apps/centbrowser/current/User Data/Default/IndexedDB/chrome-extension_fnaicdffflnofjppbagibeoednhnbjhg_0.indexeddb.blob on  HEAD (fb10e99) took 30s
🟢 > rclone tree ./ | head -n 20
/
├── 100
│   └── 00
│       ├── 2
│       ├── 3
│       ├── 4
│       └── 5
├── 1000
│   └── 00
│       ├── 2
│       ├── 3
│       ├── 4
│       └── 5
├── 1001
│   └── 00
│       ├── 2
│       ├── 3
│       ├── 4
│       └── 5
├── 1002

demo@windows10 ~/scoop/apps/centbrowser/current/User Data/Default/IndexedDB/chrome-extension_fnaicdffflnofjppbagibeoednhnbjhg_0.indexeddb.blob on  HEAD (fb10e99) took 2s
🟢 > rclone tree ./ | tail -n 20
├── ffd
│   └── 00
│       ├── 2
│       ├── 3
│       ├── 4
│       └── 5
├── ffe
│   └── 00
│       ├── 2
│       ├── 3
│       ├── 4
│       └── 5
└── fff
    └── 00
        ├── 2
        ├── 3
        ├── 4
        └── 5

19444 directories, 38883 files

demo@windows10 ~/scoop/apps/centbrowser/current/User Data/Default/IndexedDB/chrome-extension_fnaicdffflnofjppbagibeoednhnbjhg_0.indexeddb.blob on  HEAD (fb10e99)
🟢 > du ./100/00/2
4704    ./100/00/2

Expected Behavior

Auto clean IndexedDB

To Reproduce

Sync via GitHub

Debug log provided

I have provided a debug log file

Originally created by @gdm257 on GitHub (Feb 22, 2026). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2180 ### Which version of floccus are you using? 5.8.6 ### How many bookmarks do you have, roughly? about 30k ### Are you using other means to sync bookmarks in parallel to floccus? also sync via Google account ### Sync method Git ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Cent Browser 5.2.1168.83 (Chromium 134.0.6998.136) ### 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 Floccus's IndexedDB took large disk usage in several months. It is 221.9 GiB and grows indefinitely from every sync. #1913 #1915 have similar problems. ```bash # Apparent size: 221.9 GiB Items: 58327 demo@windows10 ~/scoop/apps/centbrowser/current/User Data/Default/IndexedDB/chrome-extension_fnaicdffflnofjppbagibeoednhnbjhg_0.indexeddb.blob on  HEAD (fb10e99) took 30s 🟢 > rclone tree ./ | head -n 20 / ├── 100 │ └── 00 │ ├── 2 │ ├── 3 │ ├── 4 │ └── 5 ├── 1000 │ └── 00 │ ├── 2 │ ├── 3 │ ├── 4 │ └── 5 ├── 1001 │ └── 00 │ ├── 2 │ ├── 3 │ ├── 4 │ └── 5 ├── 1002 demo@windows10 ~/scoop/apps/centbrowser/current/User Data/Default/IndexedDB/chrome-extension_fnaicdffflnofjppbagibeoednhnbjhg_0.indexeddb.blob on  HEAD (fb10e99) took 2s 🟢 > rclone tree ./ | tail -n 20 ├── ffd │ └── 00 │ ├── 2 │ ├── 3 │ ├── 4 │ └── 5 ├── ffe │ └── 00 │ ├── 2 │ ├── 3 │ ├── 4 │ └── 5 └── fff └── 00 ├── 2 ├── 3 ├── 4 └── 5 19444 directories, 38883 files demo@windows10 ~/scoop/apps/centbrowser/current/User Data/Default/IndexedDB/chrome-extension_fnaicdffflnofjppbagibeoednhnbjhg_0.indexeddb.blob on  HEAD (fb10e99) 🟢 > du ./100/00/2 4704 ./100/00/2 ``` <img width="456" height="152" alt="Image" src="https://github.com/user-attachments/assets/9d0d64c1-3bcc-4ec3-9291-720ba9f02306" /> <img width="983" height="99" alt="Image" src="https://github.com/user-attachments/assets/53558d1b-4df8-4f74-8455-02dbedcc3e6a" /> <img width="251" height="266" alt="Image" src="https://github.com/user-attachments/assets/7fedcc5c-c03b-4e7b-8c0f-4105b5513793" /> <img width="379" height="591" alt="Image" src="https://github.com/user-attachments/assets/2e43ac9e-028e-4716-b3f1-2df5bddb8c1f" /> ### Expected Behavior Auto clean IndexedDB ### To Reproduce Sync via GitHub ### Debug log provided - [ ] I have provided a debug log file

kerem

2026-02-25 22:40:05 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:40:05 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 22, 2026):

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 (Feb 22, 2026): 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:40:05 +03:00

Author

Owner

@marcelklehr commented on GitHub (Feb 22, 2026):

Hey @gdm257
Thank you for taking the time to raise this issue! I will investigate why my previous attempts to fix this were apparently not successful. As a temporary quick fix, you can uninstall the extension and reinstall it, to start with a fresh indexed db.

@marcelklehr commented on GitHub (Feb 22, 2026): Hey @gdm257 Thank you for taking the time to raise this issue! I will investigate why my previous attempts to fix this were apparently not successful. As a temporary quick fix, you can uninstall the extension and reinstall it, to start with a fresh indexed db.

kerem commented

2026-02-25 22:40:05 +03:00

Author

Owner

@marcelklehr commented on GitHub (Feb 22, 2026):

I've found a fix that will also remove all previously created database buckets from prior sync runs.

@marcelklehr commented on GitHub (Feb 22, 2026): I've found a fix that will also remove all previously created database buckets from prior sync runs.

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

No description provided.

Rows
Columns