Firefox Sync long wait for sync to happen

RESOLVED WORKSFORME

Status

()

Firefox
Sync
RESOLVED WORKSFORME
8 months ago
8 months ago

People

(Reporter: rina, Unassigned)

Tracking

51 Branch
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 months ago
Firefox Sync was slow to happen (from set up on new computer took about 3-4 hours)
Then not all bookmarks were synced, although theme, passwords etc worked great.
Ouch, that's not good. Would you mind answering a couple more questions, please?

* How many bookmarks do you have?
* Did they all sync eventually, or are you still missing some bookmarks?
* Do you see any error logs in about:sync-log, and do they contain "interesting" errors? (I think NS_ERROR_UNKNOWN_HOST is expected if your computer goes to sleep, but I'm curious if you see others from around the time you first synced).
* Could you install the About Sync add-on (https://addons.mozilla.org/en-US/firefox/addon/about-sync), open Tools > About Sync, and attach an anonymized export of your bookmarks tree? There's an "Export to file" button in the "Data provider options" section at the bottom. There should also be a "bookmarks" section with a Validation tab that might shed some light on what's going on.

Thanks!
Flags: needinfo?(rjensen)
(Reporter)

Comment 2

8 months ago
Right, I owe an apology, wrong Firefox Account.... I didn't have that many bookmarks in this one, so syncing worked perfectly. Apologies!

Still confused about the timing of the sync, but if that is known then we can close this! Sorry!
Flags: needinfo?(rjensen)
No worries, glad you got it figured out! I am a little concerned about the timing; it shouldn't take 3-4 hours.

Do you have history sync enabled? Desktop downloads your entire history at once (Android and iOS download in chunks of 5k records, IIRC). If you account has a lot of URL and form history entries, that might explain it.

Updated

8 months ago
Status: NEW → RESOLVED
Last Resolved: 8 months ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.