Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)

What steps will reproduce the problem?

  Create 10000+ of peer connection objects.

What is the expected result?

  Creation should either work, or fail in a controlled manner.

What happens instead?

  Render process crashes.

Recently, cluster fuzz has found two crashes due to resource exhaustion, https://bugs.chromium.org/p/chromium/issues/detail?id=739886 from July, and one duplicate found some week ago.

I can reproduce locally on gnu/linux, and what happens is that running the javascript creates a large number of peerconnections, and for each peerconnection, a few threads are created. At appr. 10000 peerconnections, we have appr. 32000 threads. Creating additional threads then fail, and the render process crashes at a failed CHECK in task_queue.cc.

Webrtc doesn't fail gracefully at resource exhaustion, so to avoid crashes caused by cluster fuzz, or by malicious javascript, I'd suggest enforcing some arbitrary limit on the number of peerconnections per tab. 500 might be a reasonable maximum.