Closed
Bug 972265
Opened 10 years ago
Closed 10 years ago
Use adaptive delays when trying to reconnect socket
Categories
(Firefox OS Graveyard :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: tzimmermann, Assigned: tzimmermann)
Details
Attachments
(3 files)
4.27 KB,
patch
|
qdot
:
review+
|
Details | Diff | Splinter Review |
837 bytes,
patch
|
vicamo
:
review+
|
Details | Diff | Splinter Review |
803 bytes,
patch
|
allstars.chh
:
review+
|
Details | Diff | Splinter Review |
On my Hamachi, rild constantly disconnects; probably because of incompatibilities with Gecko's RIL code. Currently, Gecko tries to reconnect after 1 second, but this just fills the logcat with warnings. A good delay for re-connects would adapt to the symptoms. So the more often the connect operation fails, the longer the delay gets. And for transient failures the delay should still remain short. This should also handle a similar problem on systems where nfcd wasn't running. Gecko tried to connect to nfcd every second, and failed on each attempt.
Assignee | ||
Updated•10 years ago
|
OS: Linux → Gonk (Firefox OS)
Hardware: x86_64 → ARM
Assignee | ||
Comment 1•10 years ago
|
||
Attachment #8375441 -
Flags: review?(kyle)
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8375444 -
Flags: review?(vyang)
Assignee | ||
Comment 3•10 years ago
|
||
Attachment #8375445 -
Flags: review?(allstars.chh)
Assignee | ||
Comment 4•10 years ago
|
||
(In reply to Thomas Zimmermann [:tzimmermann] [:tdz] from comment #1) > Created attachment 8375441 [details] [diff] [review] > [01] Bug 972265: Maintain connect delay in UnixSocketConsumer The gecko socket get's disconnected because rilproxy closes it's end when rild disconnects. I'm also working on a similar patch to improve the situation in rilproxy.
Updated•10 years ago
|
Attachment #8375444 -
Flags: review?(vyang) → review+
Comment 5•10 years ago
|
||
A follow-up for netd? On Kitkat, netd initialization takes a few seconds longer especially in emulator. Current MAX_RECONNECT_TIMES=10 scheme gives only a 10 second window and sometimes netd just can't catch the last train.
Updated•10 years ago
|
Attachment #8375441 -
Flags: review?(kyle) → review+
Attachment #8375445 -
Flags: review?(allstars.chh) → review+
Assignee | ||
Comment 6•10 years ago
|
||
(In reply to Vicamo Yang [:vicamo][:vyang] from comment #5) > A follow-up for netd? On Kitkat, netd initialization takes a few seconds > longer especially in emulator. Current MAX_RECONNECT_TIMES=10 scheme gives > only a 10 second window and sometimes netd just can't catch the last train. This could certainly be used for netd, but should be a separate bug.
Assignee | ||
Comment 7•10 years ago
|
||
https://hg.mozilla.org/integration/b2g-inbound/rev/47d5e2be3d17 https://hg.mozilla.org/integration/b2g-inbound/rev/1d1bbffa3b9f https://hg.mozilla.org/integration/b2g-inbound/rev/7736936437ba https://tbpl.mozilla.org/?tree=B2g-Inbound&rev=7736936437ba
Comment 8•10 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/47d5e2be3d17 https://hg.mozilla.org/mozilla-central/rev/1d1bbffa3b9f https://hg.mozilla.org/mozilla-central/rev/7736936437ba
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•