Code:

https://cs.chromium.org/chromium/src/content/browser/webrtc/webrtc_internals.cc?l=562&rcl=19d33c77a4173b7768bc3f7a3920a744e8b22eed

Original bug report:

 crbug.com/866200 

Reasonable behavior:

Prevent suspension when the user cares that connections stay alive

Unreasonable behavior:

Prevent suspension when there's no connected PeerConnection object

Suggested fix:

Count number of PeerConnections where IceConnectionState is "connected" or "completed" rather than just non-closed PeerConnections. For unconnected PeerConnections, nothing will time out during the suspension; for PeerConnections in "establishing" state, it's just another source of connection failure.