mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #1069] Browser sync results in huge SEELCT Query Result #711
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#711
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 @LotusAxt on GitHub (Mar 8, 2022).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1069
Which version of floccus are you using?
4.10.1
Sync method
{"label"=>"Nextcloud Bookmarks"}
Which browser are you using?
Vivaldi 5.1.2567.57 (Stable channel) (64-bit)
Which version of Nextcloud Bookmarks are you using? (if relevant)
10.1.0
Which version of Nextcloud? (if relevant)
23.0.2
What kind of WebDAV server are you using? (if relevant)
No response
Describe the Bug
If my Browser tries to sync my Bookmarks it creates the following Query (Result of 'MariaDB [(none)]> SHOW FULL PROCESSLIST\G'):
This thing runs forever on my DB and results a ~1TB temp table file, before I killed the query. (With mariaDB 10)
Expected Behavior
A sensible Query runtime.
To Reproduce
For me it happens each time the Browser on my PC tries to sync the Bookmarks.
Debug log provided
@marcelklehr commented on GitHub (Mar 8, 2022):
Please see https://github.com/nextcloud/bookmarks/issues/1661
@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.