starred/floccus

Fork 0

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

[GH-ISSUE #661] High CPU usage on Vivaldi/Chrome - Firefox OK #433

New issue

Closed

opened 2026-02-25 22:37:08 +03:00 by kerem · 7 comments

kerem commented

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

Owner

Originally created by @bhlevca on GitHub (Sep 17, 2020).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/661

Describe the bug
A clear and concise description of what the bug is.
When synchronisation starts htop shows 2 threads with 100% CPU usage for Vivaldi browser on Linux
When I kill the floccus plugin, CPUcomes back to normal.

To Reproduce
Steps to reproduce the behavior:

Go to - Start sync
Start htop
watch CPU going up
disable the pluging from the plugin manager
CPU is going down

Expected behavior
Smallt CPU impact and not 100% on 2 threads that bring the browser to a crawl

Screenshots
N/A

Desktop (please complete the following information):

OS: OpenSuse Tumbleweed
Browser : Vivaldi, Brave
Browser Version

Vivaldi	3.3.2022.45 (Stable channel) (64-bit)
Revision	a05c4d885c8da0745ffe551e567e84b9fb6a5889
OS	Linux
JavaScript	V8 8.5.210.20
Flash	32.0.0.207 /home/bogdan/.config/google-chrome/PepperFlash/32.0.0.207/libpepflashplayer.so
User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.106 Safari/537.36

Floccus version: 4.3.0
Floccus sync method: webdav

Server (please complete the following information):

OS: Opensuse tumbleweed latest
Nextcloud version: Nextcloud 19.0.1
Bookmarks app version: N/A using xbel

Debug log
N/A

Debug log provided

Additional context
N/A

Originally created by @bhlevca on GitHub (Sep 17, 2020). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/661 **Describe the bug** A clear and concise description of what the bug is. When synchronisation starts htop shows 2 threads with 100% CPU usage for Vivaldi browser on Linux When I kill the floccus plugin, CPUcomes back to normal. **To Reproduce** Steps to reproduce the behavior: 1. Go to - Start sync 2. Start htop 3. watch CPU going up 4. disable the pluging from the plugin manager 5. CPU is going down **Expected behavior** Smallt CPU impact and not 100% on 2 threads that bring the browser to a crawl **Screenshots** N/A **Desktop (please complete the following information):** - OS: OpenSuse Tumbleweed - Browser : Vivaldi, Brave - Browser Version Vivaldi | 3.3.2022.45 (Stable channel) (64-bit) -- | -- Revision | a05c4d885c8da0745ffe551e567e84b9fb6a5889 OS | Linux JavaScript | V8 8.5.210.20 Flash | 32.0.0.207 /home/bogdan/.config/google-chrome/PepperFlash/32.0.0.207/libpepflashplayer.so User Agent | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.106 Safari/537.36 - Floccus version: 4.3.0 - Floccus sync method: webdav **Server (please complete the following information):** - OS: Opensuse tumbleweed latest - Nextcloud version: Nextcloud 19.0.1 - Bookmarks app version: N/A using xbel **Debug log** N/A - [ ] Debug log provided **Additional context** N/A

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@johannes-schliephake commented on GitHub (Nov 2, 2020):

I can confirm identical behavior but using Firefox.

Desktop:

OS: macOS
Browser: Firefox
Browser Version: 82.0.2
Floccus version: 4.4.4
Floccus sync method: Nextcloud folders

Server:

OS: Ubuntu
Nextcloud version: 19.0.2
Bookmarks app version: 3.3.4

@johannes-schliephake commented on GitHub (Nov 2, 2020): I can confirm identical behavior but using Firefox. **Desktop:** - OS: macOS - Browser: Firefox - Browser Version: 82.0.2 - Floccus version: 4.4.4 - Floccus sync method: Nextcloud folders **Server:** - OS: Ubuntu - Nextcloud version: 19.0.2 - Bookmarks app version: 3.3.4

kerem commented

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

Author

Owner

@marcelklehr commented on GitHub (Nov 3, 2020):

@johannes-schliephake I recommend updating the bookmarks app

@marcelklehr commented on GitHub (Nov 3, 2020): @johannes-schliephake I recommend updating the bookmarks app

kerem commented

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

Author

Owner

@marcelklehr commented on GitHub (Jan 14, 2021):

I cannot do much about performance specific to one browser sadly. I am constantly trying to improve performance, but some browsers will probably always be worse than others.

@marcelklehr commented on GitHub (Jan 14, 2021): I cannot do much about performance specific to one browser sadly. I am constantly trying to improve performance, but some browsers will probably always be worse than others.

kerem commented

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

Author

Owner

@bhlevca commented on GitHub (Jan 14, 2021):

The problem seems to be only with the webdav file. The connection to the
nextcloud bookmark app although slower is way more reliable. I believe the
locking mechanism is the weak piece

On Thu, 14 Jan 2021 at 15:35, Marcel Klehr notifications@github.com wrote:

I cannot do much about performance specific to one browser sadly. I am
constantly trying to improve performance, but some browsers will probably
always be worse than others.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/marcelklehr/floccus/issues/661#issuecomment-760460242,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABMRXVB3TBSOSIHTSHDCIDSZ5IPLANCNFSM4RQX7WUQ
.

@bhlevca commented on GitHub (Jan 14, 2021): The problem seems to be only with the webdav file. The connection to the nextcloud bookmark app although slower is way more reliable. I believe the locking mechanism is the weak piece On Thu, 14 Jan 2021 at 15:35, Marcel Klehr <notifications@github.com> wrote: > I cannot do much about performance specific to one browser sadly. I am > constantly trying to improve performance, but some browsers will probably > always be worse than others. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/marcelklehr/floccus/issues/661#issuecomment-760460242>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AABMRXVB3TBSOSIHTSHDCIDSZ5IPLANCNFSM4RQX7WUQ> > . >

kerem commented

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

Author

Owner

@bhlevca commented on GitHub (Jan 14, 2021):

The problem seems to be only with the webdav file. The connection to the nextcloud bookmark app, although slower, is way more reliable and responsive . I believe the locking mechanism is the weak piece, but also the problem with the duplication and order of the directories is gone.

@bhlevca commented on GitHub (Jan 14, 2021): The problem seems to be only with the webdav file. The connection to the nextcloud bookmark app, although slower, is way more reliable and responsive . I believe the locking mechanism is the weak piece, but also the problem with the duplication and order of the directories is gone.

kerem commented

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

Author

Owner

@fazlerabbi37 commented on GitHub (Jul 11, 2021):

Facing this problem both in Google Chrome 91.0.4472 and Firefox 89.0.2 on Ubuntu 20.04 with Nextcloud 22.0.0 (docker) and Bookmark 4.2.2. In both case, the system becomes unusable during sync. In case of Firefox, the system was back to normal once the sync is done, but in Google Chrome the system goes in a zombie state.

@fazlerabbi37 commented on GitHub (Jul 11, 2021): Facing this problem both in Google Chrome 91.0.4472 and Firefox 89.0.2 on Ubuntu 20.04 with Nextcloud 22.0.0 (docker) and Bookmark 4.2.2. In both case, the system becomes unusable during sync. In case of Firefox, the system was back to normal once the sync is done, but in Google Chrome the system goes in a zombie state.

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Mar 20, 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.

@github-actions[bot] commented on GitHub (Mar 20, 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.

kerem referenced this issue

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

[PR #433] [CLOSED] Bump crx3 from 1.1.1 to 1.1.2 #1570

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

No description provided.

Rows
Columns