搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

Learn More

Is there a WebRTC bug in Firefox version 68.0.1?

  • 2 回覆
  • 1 有這個問題
  • 1 次檢視
  • 最近回覆由 cor-el

more options

I am part of a team that developed a WebRTC-based platform for online communications. The users who are connecting with version 68.0.1 seem to not be able to use our services at any time, as they can't upload/download any audio or video data - a "Media stream connection closed" error is given. Previous versions (e.g. 67) seem to be working. Other browsers that support WebRTC are not triggering this case.

This issue seems to occur on other similar platforms too, such as Amazon Connect, which was reported here - https://support.mozilla.org/en-US/questions/1265272

The status is "default" and the value is set to "true" for "media.peerconnection.enabled" on the device used for testing.

Since it would be quite difficult to downgrade the systems of our many users, could someone please look into this issue? Would we be able to mitigate it in any way? Hopefully, there will be a fix in the next version.

I am part of a team that developed a WebRTC-based platform for online communications. The users who are connecting with version 68.0.1 seem to not be able to use our services at any time, as they can't upload/download any audio or video data - a "Media stream connection closed" error is given. Previous versions (e.g. 67) seem to be working. Other browsers that support WebRTC are not triggering this case. This issue seems to occur on other similar platforms too, such as Amazon Connect, which was reported here - https://support.mozilla.org/en-US/questions/1265272 The status is "default" and the value is set to "true" for "media.peerconnection.enabled" on the device used for testing. Since it would be quite difficult to downgrade the systems of our many users, could someone please look into this issue? Would we be able to mitigate it in any way? Hopefully, there will be a fix in the next version.

由 HumbleUser 於 修改

所有回覆 (2)

more options

hi, can you try to use the tool at https://mozilla.github.io/mozregression/ in order to find out which change in firefox 68 caused the breakage in this case?

more options

Are there any more useful messages in the Web Console or Browser Console or Network Monitor.