Closed
Bug 1285300
Opened 10 years ago
Closed 9 years ago
Sync bookmark errors appear to drain battery
Categories
(Firefox for iOS :: Sync, defect, P3)
Tracking
()
RESOLVED
INCOMPLETE
| Tracking | Status | |
|---|---|---|
| fxios | 9.0 | --- |
People
(Reporter: osunick, Unassigned)
Details
(Whiteboard: [MobileCore])
Attachments
(1 file)
|
323.58 KB,
image/png
|
Details |
I've experienced the "Sync is experiencing issues syncing bookmarks" bug for the last week, and I haven't bothered to fix it. During this time, Firefox v5 has ballooned to 64% of my battery usage. Fixing the bookmark issue has now dropped battery usage to a reasonable amount. Can we look into this issue, and most importantly, confirm that there isn't a power consumption issue related to sync?
| Reporter | ||
Comment 1•10 years ago
|
||
Comment 2•10 years ago
|
||
If there are no new bookmarks to download, an attempt to sync involves only a cheap database check for consistency, then a real attempt to do the work. The only way it'd heavily drain battery is if the cheap check passed but the real attempt failed, and you are a heavy Firefox user (lots of bookmarks, lots of time with Firefox open on your phone).
Do you still get battery drain if you uncheck "Bookmarks" in the Sync preferences pane on your desktop?
Note: doing so will turn off bookmark sync for all of your devices, and if you re-check it, you will probably find that your bookmarks sync successfully -- the root cause of this issue is that desktop routinely uploads corrupt data to the server, and unchecking and re-checking the box will cause it to do a fresh (and likely successful) reupload.
Flags: needinfo?(nnguyen)
Hardware: Other → All
| Reporter | ||
Comment 3•10 years ago
|
||
Yes, this appears to be the case. If I uncheck 'bookmarks' as per the workaround then battery usage drops dramatically.
Flags: needinfo?(nnguyen)
Comment 4•10 years ago
|
||
How many bookmarks do you have, Nick?
sqlite3 places.sqlite "SELECT COUNT(*) FROM moz_bookmarks"
in your profile directory should work.
We shouldn't bother trying again if the last merge attempt failed for inconsistency and nothing new has been buffered since the last attempt. Emily, did any work along those lines make it into the tree?
Flags: needinfo?(nnguyen)
Flags: needinfo?(etoop)
Comment 5•10 years ago
|
||
I don't believe any of that work has made it into the current codebase. It was one of the next things on the list to tackle.
Flags: needinfo?(etoop)
Updated•10 years ago
|
Priority: -- → P1
Updated•10 years ago
|
Whiteboard: [MobileAS Backlog]
Updated•10 years ago
|
Priority: P1 → --
Updated•10 years ago
|
Whiteboard: [MobileAS Backlog] → [MobileAS]
Updated•10 years ago
|
Priority: -- → P3
Updated•10 years ago
|
Rank: 1
Priority: P3 → P2
Updated•9 years ago
|
Whiteboard: [MobileAS] → [MobileAS] [MobileCore]
Updated•9 years ago
|
Whiteboard: [MobileAS] [MobileCore] → [MobileCore]
Updated•9 years ago
|
tracking-fxios:
--- → 7.0+
Priority: P2 → P3
Updated•9 years ago
|
Updated•9 years ago
|
Updated•9 years ago
|
Status: NEW → UNCONFIRMED
Rank: 1 → 2
Ever confirmed: false
Comment 7•9 years ago
|
||
Closing this bug because we have seen no evidence of this recently.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•