Closed
Bug 565714
Opened 14 years ago
Closed 14 years ago
Multiple tabs records from the current client after canceling setup multiple times
Categories
(Firefox :: Sync, defect)
Firefox
Sync
Tracking
()
RESOLVED
DUPLICATE
of bug 565430
People
(Reporter: Mardak, Unassigned)
Details
Attachments
(1 file)
86.62 KB,
image/png
|
Details |
Ragavan ran into this when testing out various setup paths by canceling. We do reset all prefs when canceling setup, but not entirely sure why we have multiple tab records. But the logs show that multiple tab records are uploaded from the current client when it actually finishes sync. So perhaps somehow tab changes are stored locally in the tab tracker even when resetting stuff.
Comment 1•14 years ago
|
||
maybe Weave.Service.startOver() should nuke the stuff in <profile>/weave ?
Reporter | ||
Comment 2•14 years ago
|
||
It would lose out on timestamps of changes that happened from before startOver. And that the code uses stuff in memory and not from disk after the service is running.
Comment 3•14 years ago
|
||
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•6 years ago
|
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in
before you can comment on or make changes to this bug.
Description
•