From posting on discuss-webrtc by Fred.clark@connectuscom.com:

"I have a particular laptop that seems to crash Chrome when I exit a WebRTC video/audio call.  I do a lot of testing of this WebRTC application.  It normally works fine, but when I connect my desktop and my laptop and then try to close, Chrome on the laptop crashes.  At that point there is nothing I can do about it except to wait for about 2 to 3 minutes.  Then it clears itself and all is fine.

Here is a list of devices that I normally use to test with:
1.  HP desktop Windows 10 64 bit.  Very fast and lots of memory.
2. Toshiba laptop  Windows 10 64 bit.  The Problem hardware.
3. Android Asus tablet vs 6.0
4.Samsung S5 phone vs 6.0
5. Surface Pro 3 Windows 10 64 bit

I only have a problem between the HP desktop and the Toshiba laptop and then only the laptop has the problem.  Calls between the laptop and other remote users is also not a problem.  These two PC's are on the same LAN.

I have recently tuned up this laptop and also deleted all extensions from Chrome.  Nothing else on the laptop seems to be a problem.  We have added diagnostics to the application, but it doesn't appear to be an application problem.  It appears to be more of a Chrome issue.  Using Chrome 57."


Attached is a chrome://tracing trace. Note that Chrome isn't actually crashing, but rather hanging for two minutes. Though, not being very experienced at looking at traces, I didn't see anything that stood out to me. PeerConnection::Close by itself completes quickly, so it's not even clear if this issue is webrtc-related or not.

Hoping someone else with more experience debugging Chrome issues can glean something the from the trace I couldn't.
 

Deleted: trace_webrtc-chrome_hang_problem.json.gz 7.1 MB

trace_webrtc-chrome_hang_problem.json.gz 7.1 MB Download