Closed
Bug 1157766
Opened 10 years ago
Closed 10 years ago
Firefox 37 only supports 16 datachannels
Categories
(Core :: WebRTC: Networking, defect, P1)
Tracking
()
RESOLVED
FIXED
mozilla40
People
(Reporter: bemasc, Assigned: jesup)
References
(Blocks 1 open bug)
Details
(Keywords: regression, Whiteboard: [webrtc-uplift])
Attachments
(1 file)
1.71 KB,
patch
|
bwc
:
review+
Sylvestre
:
approval-mozilla-aurora+
Sylvestre
:
approval-mozilla-release+
|
Details | Diff | Splinter Review |
User Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/44.0.2369.0 Safari/537.36
Steps to reproduce:
Go to http://mozilla.github.io/webrtc-landing/data_test.html
Click Start!
Open the console
pc2.ondatachannel = function(e) { console.log("ondatachannel with label", e.channel.label); };
pc1.createDataChannel("1");
> "ondatachannel with label" "1"
pc1.createDataChannel("2")
> "ondatachannel with label" "2"
pc1.createDataChannel("3")
> "ondatachannel with label" "3"
pc1.createDataChannel("4")
> "ondatachannel with label" "4"
pc1.createDataChannel("5")
> "ondatachannel with label" "5"
pc1.createDataChannel("6")
> "ondatachannel with label" "6"
pc1.createDataChannel("7")
> "ondatachannel with label" "7"
pc1.createDataChannel("8")
pc1.createDataChannel("9")
The receiver never gets channels 8 or 9.
Actual results:
Only the first 7 channels are received
Expected results:
All channels received.
Reporter | ||
Updated•10 years ago
|
OS: Unspecified → All
Hardware: Unspecified → All
Version: 33 Branch → 37 Branch
Comment 1•10 years ago
|
||
firefox-37.0.2.en-US.linux64
2015-04-23-03-02-04-mozilla-central-firefox-40.0a1.ru.linux-x86_64
Reproduced as described, according to the output on the page.
Component: Untriaged → WebRTC
Product: Firefox → Core
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → rjesup
Status: UNCONFIRMED → ASSIGNED
status-firefox37:
--- → wontfix
status-firefox38:
--- → affected
status-firefox39:
--- → affected
status-firefox40:
--- → affected
Component: WebRTC → WebRTC: Networking
Ever confirmed: true
Assignee | ||
Comment 2•10 years ago
|
||
Attachment #8596775 -
Flags: review?(docfaraday)
Comment 3•10 years ago
|
||
Comment on attachment 8596775 [details] [diff] [review]
mismatched DataChannel initial channel size in JSEP database breaks adding channels
Review of attachment 8596775 [details] [diff] [review]:
-----------------------------------------------------------------
Looks fine.
Attachment #8596775 -
Flags: review?(docfaraday) → review+
Assignee | ||
Comment 4•10 years ago
|
||
Regressed in 37; 36 is good.
Assignee | ||
Comment 5•10 years ago
|
||
Assignee | ||
Comment 6•10 years ago
|
||
[Tracking Requested - why for this release]:
Recent regression; affects some applications are badly affected
tracking-firefox38:
--- → ?
Assignee | ||
Comment 7•10 years ago
|
||
Comment on attachment 8596775 [details] [diff] [review]
mismatched DataChannel initial channel size in JSEP database breaks adding channels
Approval Request Comment
[Feature/regressing bug #]: bug 1079729 (probably, or perhaps that plus the JSEP signaling rewrite in 37)
[User impact if declined]: Inability to create more than 8 datachannels from each end (16 total)
[Describe test coverage new/current, TreeHerder]: Manual testing via the data_test.html page.
[Risks and why]: Very low risk; risk is almost solely that expansion isn't tested often (filed bug for that; should have coverage soon). Alternatively we could effectively land the 36 patch on 38 (to up the limit to 256 and not allow increases), and then take this on 40 and 39. Or more to the point, land this (to default to 256 always) and add a simple error return in place of requests to increase the number (i.e. the 36 patch).
[String/UUID change made/needed]: none
Attachment #8596775 -
Flags: approval-mozilla-beta?
Attachment #8596775 -
Flags: approval-mozilla-aurora?
Assignee | ||
Comment 8•10 years ago
|
||
> Approval Request Comment
> [Feature/regressing bug #]: bug 1079729 (probably, or perhaps that plus the
> JSEP signaling rewrite in 37)
I checked, the bug crept in during the rewrite of the signaling for 37 (constant change landed after code was copied to form the basis of the JSEP implementation I imagine).
> [Risks and why]: Very low risk; risk is almost solely that expansion isn't
> tested often (filed bug for that; should have coverage soon). Alternatively
> we could effectively land the 36 patch on 38 (to up the limit to 256 and not
> allow increases), and then take this on 40 and 39. Or more to the point,
> land this (to default to 256 always) and add a simple error return in place
> of requests to increase the number (i.e. the 36 patch).
Actually the 36 patch did leave expansion working, but upped the default to 256 from 16. This means 36/35/34 had this fixed and with working expansion, and some developers were hitting it (which is how bug 1079729 was filed). This patch simply restores that behavior.
Comment 9•10 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla40
Comment 10•10 years ago
|
||
Comment on attachment 8596775 [details] [diff] [review]
mismatched DataChannel initial channel size in JSEP database breaks adding channels
[Triage Comment]
Should be in 38 beta 8
Attachment #8596775 -
Flags: approval-mozilla-release+
Attachment #8596775 -
Flags: approval-mozilla-beta?
Attachment #8596775 -
Flags: approval-mozilla-aurora?
Attachment #8596775 -
Flags: approval-mozilla-aurora+
Comment 11•10 years ago
|
||
Comment 12•10 years ago
|
||
Comment 13•10 years ago
|
||
Updated•10 years ago
|
Updated•10 years ago
|
status-firefox38.0.5:
--- → fixed
Comment 14•10 years ago
|
||
Reproduced the original issue (limited number of channels received) using Firefox 38 Beta 8. The issue no longer reproduces as the number of channels is no longer limited, when using Firefox 38 Beta 9, on Windows 7 x64, Mac OS X 10.10, Ubuntu 14.04 x64.
You need to log in
before you can comment on or make changes to this bug.
Description
•