[GH-ISSUE #287] Am seeing bookmarks duplicated regularly in mass quantities ... #263

Closed
opened 2026-02-25 22:36:38 +03:00 by kerem · 8 comments
Owner

Originally created by @bernd-wechner on GitHub (May 11, 2019).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/287

This has been happening for months I've lost track of when it started, because it's rare enough that I just fix it and move on. But it's still happening so wanted to log an issue to see if it can be diagnosed.

Software versions

  • Browser: Firefox and Google Chrome
  • Nextcloud: Nextcloud version | 15.0.6.1, NextCloudPi version | v1.12.0
  • Nextcloud Bookmarks app: 1.0.3
  • Floccus: 3.2.16
  • Floccus sync method: Nextcloud Bookmarks with Folders

Steps to reproduce

Nothing. It just happens ;-).

Expected outcome

That I don't get bookmarks duplicated en masse.

Actual outcome

Selective bookmarks are duplicate en mass at time

Debug log

  • Debug log provided (floccus-3.2.16-2019-05-11.log)

A screen image may be useful:

image

obfuscated irrelevant bookmarks:

image

To be clear, I see this on difference folders, on different sites, but it's always one site in a folder or two that just multiply with these # string versions. I am not bookmarking them, they are just appearing. I regularly delete them. No idea where they come from.

Originally created by @bernd-wechner on GitHub (May 11, 2019). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/287 This has been happening for months I've lost track of when it started, because it's rare enough that I just fix it and move on. But it's still happening so wanted to log an issue to see if it can be diagnosed. ### Software versions - Browser: Firefox and Google Chrome - Nextcloud: Nextcloud version | 15.0.6.1, NextCloudPi version | v1.12.0 - Nextcloud Bookmarks app: 1.0.3 - Floccus: 3.2.16 - Floccus sync method: Nextcloud Bookmarks with Folders ### Steps to reproduce Nothing. It just happens ;-). ### Expected outcome That I don't get bookmarks duplicated en masse. ### Actual outcome Selective bookmarks are duplicate en mass at time ### 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 to the issue here, publicly, I recommend uploading it privately at the following URL https://klehranlage.net/index.php/s/7nn82NSBsfQKdsJ --> - [x] Debug log provided (floccus-3.2.16-2019-05-11.log) <!-- Thanks! Now, hit Submit and wait for a reply :) --> A screen image may be useful: ![image](https://user-images.githubusercontent.com/7296506/57568510-b45e3780-742b-11e9-97a2-76fcbdacf209.png) obfuscated irrelevant bookmarks: ![image](https://user-images.githubusercontent.com/7296506/57568536-099a4900-742c-11e9-8457-81acb110a604.png) To be clear, I see this on difference folders, on different sites, but it's always one site in a folder or two that just multiply with these # string versions. I am not bookmarking them, they are just appearing. I regularly delete them. No idea where they come from.
kerem closed this issue 2026-02-25 22:36:38 +03:00
Author
Owner

@marcelklehr commented on GitHub (May 15, 2019):

I believe I've found the culprit. The next new release of the bookmarks app should fix this.

<!-- gh-comment-id:492736088 --> @marcelklehr commented on GitHub (May 15, 2019): I believe I've found the culprit. The ~~next~~ new release of the bookmarks app should fix this.
Author
Owner

@marcelklehr commented on GitHub (May 16, 2019):

Can you confirm if this fixed things for you?

<!-- gh-comment-id:493054562 --> @marcelklehr commented on GitHub (May 16, 2019): Can you confirm if this fixed things for you?
Author
Owner

@bernd-wechner commented on GitHub (May 16, 2019):

In time perhaps. The problem of course is that it was intermittent. I can't see it on the browser I'm now (FF on Windows 10) which I cleaned up when I filed this. I just went to Chrome on same box and it does, butt hat's legacy, that I haven't cleaned up, so I've cleaned that up now. Then the waiting game begins. Basically if a month or two pass and I've not seen the problem recur I'd be happy to drop back in and say, yep, fixed! This sadly was not a problem I had good steps to reproduce, just an intermittent observation affecting fairly random sites out of the blue, but a subset of the total.

If from your code check you think you have steps to reproduce it I can try. I mean it might be that visiting a given bookmark or simply adding a given type of bookmark is what triggered it?

<!-- gh-comment-id:493269274 --> @bernd-wechner commented on GitHub (May 16, 2019): In time perhaps. The problem of course is that it was intermittent. I can't see it on the browser I'm now (FF on Windows 10) which I cleaned up when I filed this. I just went to Chrome on same box and it does, butt hat's legacy, that I haven't cleaned up, so I've cleaned that up now. Then the waiting game begins. Basically if a month or two pass and I've not seen the problem recur I'd be happy to drop back in and say, yep, fixed! This sadly was not a problem I had good steps to reproduce, just an intermittent observation affecting fairly random sites out of the blue, but a subset of the total. If from your code check you think you have steps to reproduce it I can try. I mean it might be that visiting a given bookmark or simply adding a given type of bookmark is what triggered it?
Author
Owner

@marcelklehr commented on GitHub (May 17, 2019):

I believe this would occur only with URLs that contain a fragment portion (#fragment) and is possibly triggered by new updates to floccus, which reset the cache. So, to trigger something like this, you might want to reset the cache (trigger sync from scratch) and hit sync.

<!-- gh-comment-id:493512405 --> @marcelklehr commented on GitHub (May 17, 2019): I believe this would occur only with URLs that contain a fragment portion (`#fragment`) and is possibly triggered by new updates to floccus, which reset the cache. So, to trigger something like this, you might want to reset the cache (trigger sync from scratch) and hit sync.
Author
Owner

@marcelklehr commented on GitHub (Jun 13, 2019):

Any news?

<!-- gh-comment-id:501772359 --> @marcelklehr commented on GitHub (Jun 13, 2019): Any news?
Author
Owner

@bernd-wechner commented on GitHub (Jun 14, 2019):

Sadly no, have been far too busy to pay much heed to this. But that said, your prompt is welcome (arrives by email as I have a watch on the thread) and what I can do is confirm:

  1. I've not seen the problem recur.
  2. Scanning my bookmarks quickly I find one (https://calendar.google.com/calendar/render#main_7) that seems to fit your causality description and it's not been duplicated.

Perhaps that suffices as a confirmation?

<!-- gh-comment-id:501936022 --> @bernd-wechner commented on GitHub (Jun 14, 2019): Sadly no, have been far too busy to pay much heed to this. But that said, your prompt is welcome (arrives by email as I have a watch on the thread) and what I can do is confirm: 1. I've not seen the problem recur. 2. Scanning my bookmarks quickly I find one (https://calendar.google.com/calendar/render#main_7) that seems to fit your causality description and it's not been duplicated. Perhaps that suffices as a confirmation?
Author
Owner

@marcelklehr commented on GitHub (Jun 14, 2019):

Good enough for me :) If it ever pops up again, just shoot an issue ;)

<!-- gh-comment-id:502062510 --> @marcelklehr commented on GitHub (Jun 14, 2019): Good enough for me :) If it ever pops up again, just shoot an issue ;)
Author
Owner

@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.

<!-- gh-comment-id:1477489149 --> @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.
Sign in to join this conversation.
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#263
No description provided.