Bookmark sync fails from desktop to mobile with 1152 bookmarks
Categories
(Firefox :: Sync, defect, P3)
Tracking
()
People
(Reporter: rasiersoftware, Unassigned)
Details
Attachments
(1 file)
|
82.89 KB,
image/png
|
Details |
AboutSyncConsoleView.png
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:70.0) Gecko/20100101 Firefox/70.0
Firefox for Android
Steps to reproduce:
Force a sync through Sync Now
Actual results:
No bookmarks not syncing to Firefox for iOS (or a 2nd desktop copy of Firefox).
Expected results:
Bookmarks should have synced.
RELEVANT LOGFILES:
About:Support- https://privatebin.net/?79bcde67c0474f4c#ELxuySNEdiTi3xWdPH2vCuoLu1yyehbDW76p6zDoXCez
About:Sync-Log from FF 70.0.01 (1 of 2)- https://privatebin.net/?95c9431bc1818456#5wjhYJbVVgjxJibQkLUYMKnqCtJBoRfSmrkcqQBh2eCS
About:Sync-Log from FF 70.0.01 (2 of 2)- https://privatebin.net/?adac677bd68d0514#41nDtKVkzxKiR6qVzcjhWQR1o4jfBUaAXUYRdXvquchU
About:Sync-Log from FF 72.0a1 (2019-11-06) with the 'About Sync' addon (1 of 2)- https://privatebin.net/?a31b3897d681dbbe#4X7grXfiGXfKVk8TShXhwFvSDLcCxRitcSiYLsdfAt6F
About:Sync-Log from FF 72.0a1 (2019-11-06) with the 'About Sync' addon (2 of 2)- https://privatebin.net/?59aea5295699af35#4Zej8HW2ZDT3t5eTjX4pwy7PqghcAw91MNxhY91Z5FyP
ATTEMPT TO RESOLVE:
about:sync-log->disconnect FF account on ALL syncing devices->delete mobile app(s)->about:support-> Places Database->Verify Integrity->close FF->reopen and run Verify integrity again->sync each device one at a time individually after another. No change in outcome.
|
||
Comment 1•6 years ago
|
||
Bugbug thinks this bug should belong to this component, but please revert this change in case of error.
|
||
Comment 2•6 years ago
|
||
It appears that you have ~113,000 bookmarks - sync is never going to do a great job with this. iOS in particular is likely to have a lot of trouble. In at least one of the logs, a desktop device is trying to download all of these, which is taking over 5 minutes - however, before it gets to finish, some other device has added a new bookmark, so the new device stops and needs to try again later. Given the huge number of bookmarks, it wouldn't surprise me to find this happens quite often.
The only think I can suggest is that you try and keep your bookmark count to below 20k or so.
I don't have 113K bookmarks (not even close), that may be bookmark history though. I'm not getting bookmarks to sync anywhere, iOS or other desktop installs. The LiveMarks addon emulated Mozilla's removed RSS Live Bookmark support and places updates in the Bookmarks Menu. It doesn't store all of them, which is why I think that's the history.
My thought was that Firefox Sync is holding onto old synced bookmarks on the backend even though they're no longer active/removed and that there's a design issue there in this regard.
I just did a count and I have 1152 bookmarks, including the RSS feed folders.
|
|
||
Comment 5•6 years ago
|
||
I understand you think you only have 1152 bookmarks. The screenshot you added shows how many about:sync thinks you have and one of the logs says:
1573098330939 Sync.Engine.Bookmarks INFO Records: 31 applied, 31 successfully, 0 failed to apply, 0 newly failed to apply, 1134764 reconciled.
I read the screenshot wrong - it's 1.13 million :) And it's bookmarks, not history - although there's a reasonable chance these are tombstones (ie, old deleted bookmarks) and the items inside the RSS feed folders count.
I also use the livemarks addon - an old version of this caused this symptom, but it was largely addressed in recent updates - see bug 1499881. On a device with all the bookmarks you care about, can you please de-select bookmarks from about:preferences#sync, then force a "sync now", then re-enable bookmarks, force another sync now, and upload the new logs which will have been created? This should delete all the old "tombstones" from the server and is likely to fix the issue.
I got the 1,152 number from exporting my bookmarks to a file and doing a count. Either way, what you suggested did fix it. Thank you. They started showing up on iOS immediately. My next step was to delete and recreate my FF account which I knew would work (thinking LiveMarks was hitting some sort of Sync ceiling in history/tombstone records), but I wanted to put in the effort to resolve this issue for other users as the root cause could affect them even years from today. It may be possible to be self-healing in regards to a given threshold of tombstone records.
about:sync-log produced nothing at all, not a single error must've come through. If there's anything else I can share to help Mozilla improve this I'll be happy to dig it up, I want other users to have a great experience as I've been using Firefox since it was Phoenix and never left! Thanks again.
I should add that the only casualty in this has been my mobile bookmarks folder. That was somehow deleted, but it appears it was done long ago. Restoring older backups from Import and Backup don't have those either. Otherwise, I repeated the process (unchecking the Bookmarks category) in Sync but for every option, hoping to clean up any other legacy issues that may be hanging around.
If not placing a threshold for truncating tombstone records, eg. deleting them all once they reach 50K or so, then maybe it would be ideal to have a full sync clear (equivalent of unchecking every category, syncing, and then checking them all and syncing)- as part of the Firefox reset/tune-up troubleshooting option. It would probably be good for Mozilla's server as well as their users, my sync is running far better now. I had a very poor impression of Firefox Sync for the longest time. It would make sense to monitor some health metrics and pop up an advisory to the user to run a tune-up that does this and other maintenance tasks. Just some ideas.
|
|
||
Comment 8•6 years ago
|
||
Thanks for the suggestions, but unfortunately I don't see how they are actionable in the general case. If we do find this happens due to other extensions, I suspect we might end up creating a bug that throttles the number of bookmarks an extension can create, and there's nothing to suggest this problem can happen for any other reason. Some of the other mitigations you suggest would actually be expensive in the general case (eg, working out whether there are 50k tombstones would have a large impact for any users with a significant number of bookmarks without a large number of tombstones).
We're sorry the the inconvenience this caused though, and we'll keep thinking about ways we might have avoided this situation.
Description
•