New issue
Advanced search Search tips

Issue 736306 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chrome tab crashes on multiple WebRTC connections being created (not even connected)

Reported by nazar.mo...@gmail.com, Jun 23 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0

Steps to reproduce the problem:
Demo (increase number of connections to reproduce: https://jsfiddle.net/3jmk6d20/
1. Try to create 200 RTCPeerConnection connections

What is the expected behavior?
Connections are created and they number is only limited by hardware capabilities

What went wrong?
Browser tab crashes on 150..165 connections created

Did this work before? No 

Does this work in other browsers? Yes

Chrome version: 61.0.3140.0  Channel: canary
OS Version: Ubuntu 17.10 x64
Flash Version: 

My use case if implementing DHT that works in browsers and this is a serious limiting issue for me. I can potentially somehow deal with exceptions, but not with tabs crashing all the time.

To be fair, Firefox Nightly tab freezes instead of crashing and manages to create few dozens more connections than Chromium nightly.
 
Similar Firefox bug report: https://bugzilla.mozilla.org/show_bug.cgi?id=1375818
Much easier demo: https://jsfiddle.net/jib1/3jmk6d20/3/
Just calling RTCPeerConnection constructor a bunch of times is enough for tab to crash.

Comment 3 by guidou@chromium.org, Jun 26 2017

Components: -Blink>WebRTC Blink>WebRTC>PeerConnection
Owner: guidou@chromium.org
Status: Assigned (was: Unconfirmed)

Comment 4 by guidou@chromium.org, Mar 14 2018

Status: Fixed (was: Assigned)
This has been fixed by new limits on the number of peer connections a page can create.
The crash no longer reproduces.
What new limits are? Will tab still crash when limits are faced?

Sign in to add a comment