1310121 - Can't display more than five MediaStream include audio on single instance

Status: NEW

(Core :: WebRTC: Audio/Video, defect, P3)

Description

[mengjiu.tsao]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce:

When I use the WebRTC sample link to test the maximum MediaStream numbers that client can play at the same time and on single Firefox process instance. I found that if MediaStream include audio, the maximum numbers is five. The sixth page MediaStream can't display throw by RTCPeerConnection. But if MediaStream doesn't include audio,then the maximum numbers is raise than five. I have provide the video which record those steps and attach the video file in this bug.

By the way, this situation only occur on windows platform. When I use the same test on the other platform, there is no maximum numbers is five limit (e.g., iOS 10.11.6 / Firefox 49.0.1, Ubuntu 14.04/Firefox 49.0).

Those are the steps:
1.Open a new page with this link. 
  https://webrtc.github.io/samples/src/content/peerconnection/multiple-relay/
  This link is from WebRTC sample which demo [Forward the output of one PC into another].(https://webrtc.github.io/samples/) 
2.Check the [Include audio] checkbox.
3.Press the [Start] button and choose the shared device, include the camara and microphone. Then the left video element will display the MediaStream.
4.Press the [Call] button. Then the right video element will display the MediaStream throw by RTCPeerConnection.
5.Repeat the 1 to 4 step to open six pages.


Actual results:

The sixth page MediaStream can't display throw by RTCPeerConnection at the right video element. And there is maximum numbers is five limit.


Expected results:

The sixth page MediaStream can display throw by RTCPeerConnection at the right video element. And there is no maximum numbers is five limit.

Comment 1

[mengjiu.tsao]

Here is the video which record those steps on YouTube Website.
https://youtu.be/YFwDsxbuWv8

Comment 2

[Loic]

FF33 has the same behaviour, not a new issue.

Comment 3

[Bulk Bug Changes for mreavy's org]

Mass change P2->P3 to align with new Mozilla triage process.