Closed
Bug 692704
Opened 14 years ago
Closed 14 years ago
Sync Error - history failed: NS_ERROR_NET_RESET JS Stack trace: Res_post()@resource.js:487
Categories
(Firefox :: Sync, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: tchung, Unassigned)
Details
Attachments
(1 file)
10.13 KB,
text/rtf
|
Details |
Been hitting this sync error today.
1317946607419 Sync.Service DEBUG Exception: Could not acquire lock. Label: "service.js: sync". No traceback available
See attached log.
Repro:
1) launch mac nightly: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:10.0a1) Gecko/20111005 Firefox/10.0a1
2) setup sync
3) verify error syncing
Expected:
- no error on failed history and sync lock
Comment 1•14 years ago
|
||
What was the UX? Have you been seeing Sync error bars?
Comment 2•14 years ago
|
||
Seeing NS_ERROR_NET_RESET in logs is perfectly normal if the servers are having problems keeping up with the request load. "Could not acquire lock" makes sense too. You're trying to kick off a sync while another one is still running, presumably because the requests are taking a long time to be processed by the server (because it's under heavy load.)
These are errors that Sync deals with internally. Just because they pop up in the log doesn't mean something's actually wrong. So long as they're not shown to the user, everything is fine.
Please reopen if you saw an error bar.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Reporter | ||
Comment 3•14 years ago
|
||
correct, no error bar for this scenario.
Status: RESOLVED → VERIFIED
Assignee | ||
Updated•7 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
•