mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 14:45:59 +03:00
[GH-ISSUE #235] Chrome shows errors on the extension page #226
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#226
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 @akidburn on GitHub (Feb 22, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/235
Hi,
Chrome shows errors on the extension page if debuging and error loging for floccus is activated.
for floccus 3.2.6 it shows:
and after syncing failed with there is a stacktrace attached.

Both Chrome and Firefox were way slower since the last update, and cpu usage was higher than normal.
Please fix
akidburn
@marcelklehr commented on GitHub (Feb 28, 2019):
Hey @akidburn
The warnings are due to cross-browser support. The Error is simply a sync error that is also shown in the UI.
The fact that performance seems to have degraded could be due to a recent fix that filters out duplicates that were introduced by an earlier floccus version. I've just commited a patch that should speed up that code a little, but it shouldn't be needed much longer than a few versions, as it basically acts as a kind of migration. The performance drop could also be due to other changes, though :/
@marcelklehr commented on GitHub (Mar 9, 2019):
Has performance improved for you meanwhile?
@github-actions[bot] commented on GitHub (Mar 21, 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.