mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 06:35:59 +03:00
[GH-ISSUE #929] Floccus sometimes hangs parts of Firefox UI #600
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#600
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @mnalis on GitHub (Aug 6, 2021).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/929
Describe the bug
Sometimes, when Floccus shows blue
<->on it's icon to indicate it is syncing, firefox will behave strangely with parts of UI "hanged". Eg. when I try to click on icon of some extension (like floccus or any other: foxyproxy, textarea cache, uBlock origin) it will not open that extension window, but will instead just show a white triangle below extension icon - the triangle that normally expands to extension window). I can click on other existing tabs, and even open a new tab, but I cannot open any real URL in that new tabs - it just stands there. Firefox menus work though, as doesabout:Configinternal URL.First time I closed Firefox to recover, but second time it seems to recover by itself after several minutes (maybe dozen?)
To Reproduce
Not quite sure. It happened twice so far today, but I've been unable to reproduce it at will.
Seems to happen only while floccus shows it is syncing.
I have 3 syncs enabled to same nextcloud account but different remote directories:
Bookmarks Toolbar,Bookmarks menu,sync tabs.Expected behavior
UI continuing to work normally while Floccus is syncing.
Screenshots
Example hang - as I see it does not open any content for github URL, also the white triangle is shown as I try to open floccus extension window but it won't open it:

Desktop
Server
Debug log
It is often useful to provide a debug log file along with the issue. You can obtain a debug log of the most recent sync runs by clicking 'Debug log' in the bottom right corner of the floccus panel in your browser.
Note: As your debug log usually contains large parts of your bookmark data, instead of attaching it publicly to the issue here, I recommend uploading it privately at the following URL https://cloud.marcelklehr.de/s/PCi3iLWrzdMZSmw
Additional context
I never noticed this problem in previous Floccus
v4.6.4, butSync tabswas disabled then too (because of https://github.com/floccusaddon/floccus/issues/883 and https://github.com/floccusaddon/floccus/issues/912)Might be related or not:
first time I synced tabs after upgrading floccus, after few dozen minutes it started closing and reopening what seems like all tabs (including tabs I'm sure I haven't changed since initial tabs sync attempts, eg. for months). Each one was in "loading" state (usually my firefox is setup to only try loading tabs once I click on them, and not to load them all automatically on eg. restart), and since I have several hundred of tabs it slowed firefox considerably, so I went to do other things on the computer while all those tabs load.
However some 20 minutes after I stopped watching firefox (so 40-50 minutes after a sync start), I've noticed general sluggishness, and was surprised to see Firefox was still syncing and has eaten all 8GB of RAM and 8GB of swap. I was soon forced to click
xto close Firefox, which worked. After that I opened and synced tabs manually and after some time this bug occurred.After I restarted firefox and synced tabs again, it worked and said tabs are synced successfully.
Some time after that, while it was syncing automatically (or it might have been me playing with manual sync before and sync not being completed yet, I'm not sure), floccus experienced the bug again - this time it recovered by itself after some dozen minutes or so.
@TeutonJon78 commented on GitHub (Feb 22, 2022):
Not sure if I'm essentially running into the same problem, or if it overlaps with #1011. I have a decent number of bookmarks (probably into the thousands over the years of collecting them). But every time Floccus goes to sync (sync to GDrive, Floccus 4.10.1, FF 97.0.1, so all up to date), it basically completely stalls out Firefox for about 40-60 seconds. I can open tabs and scroll existing pages, but it basically kills the internet connection side. No pages will load. After it finishes some part of the sync, the connection will start working again. It will be fine until the next sync starts.
It's not a problem with the internet connection in general, because I can still use other browsers or internet things at the same time and they continue to work just fine.
@marcelklehr commented on GitHub (Feb 26, 2022):
I may have been able to improve this situation with #1053 (by not constructing a hash tree for the whole bookmarks tree anymore which presumably would block a lot of CPU cycles).
@marcelklehr commented on GitHub (Feb 26, 2022):
I'd be grateful, if you could help test whether this makes a difference. I'll provide you with an alpha build.
@pawlosck commented on GitHub (Mar 2, 2022):
It looks like similar to my problem. I am using floccus and nextcloud. When floccus starts syncing, firefox is freezed and I can't do anything with firefox. Firefox consumes over 100% of one core.
Today, I left my laptop for few hours, to check, what will be happen and after 3-4h, I saw a lot of messages like this "E017: Network error: Check your network connection and your account details".
Bookmarks was saved in nextcloud, so generally is ok, but freezed firefox and one core consumed by firefox is not good.
I checked apache logs, nextcloudd logs and floccus logs and I didn't see any strange logs except problems with internet connection reported by floccus.
@TeutonJon78 commented on GitHub (Mar 8, 2022):
I'd be happy to try the test build.
@marcelklehr commented on GitHub (Mar 9, 2022):
Here you go:
I've already had one report of it not working, sadly, but I'm always glad about more testers.
https://github.com/floccusaddon/floccus/releases/tag/v4.11.0-alpha.0
@pawlosck commented on GitHub (Mar 9, 2022):
Is it stable? I mean, is it safe for my bookmarks? Alpha versions are not stable in most of projects.
@marcelklehr commented on GitHub (Mar 9, 2022):
It passed all automated tests at the time, but I generally recommend making backups when using floccus.
@TeutonJon78 commented on GitHub (Mar 16, 2022):
Is there any way to install it on normal Firefox? It seems unsigned addons can only be installed in daily or dev builds.
@marcelklehr commented on GitHub (May 24, 2022):
You may be able to install it at about:debugging -> This firefox -> Load temporary addon
@exstntlmsnthrp commented on GitHub (Jun 16, 2022):
I agree with @TeutonJon78, this seems at minimum very closely related to issue 1011, which I replied to before finding this. As I commented there, I have most of the same issues referenced in this issue, except with Nextcloud.
I have done similar to what @pawlosck says in their comment as well. Although, for me Firefox will crash before it gets that long.
@marcelklehr commented on GitHub (Oct 7, 2022):
Since #1011 was fixed can you confirm whether this issue is resolved with the latest version of floccus as well?
@pawlosck commented on GitHub (Oct 7, 2022):
I am using floccus 4.17.1 with merge mode. Since about two months or more, everything is ok. One minute ago I checked adding new bookmark and removing bookmark from nextcloud and no problems.
@github-actions[bot] commented on GitHub (Oct 15, 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.