Issue metadata
Sign in to add a comment
|
RTCPeerConnection.close() can hang the UI thread for a second or two
Reported by
ja...@jamesandjo.com,
Aug 17 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36 Steps to reproduce the problem: 1. Create a WebRTC session with two peers (I used AppRTC sample) 2. Quickly hang-up one of the peers 3. Observe the brief UI hang. If the hang doesn't occur, try again (try hanging-up the other peer) 4. If you put a breakpoint around the call to RTCPeerConnection.close(), you can sometimes see the call takes 500ms - 2s to return Anecdotally, the shorter the RTC call is open, the more likely the hang is to occur, and the longer it is likely to be. What is the expected behavior? RTCPeerConnection.close() should always return immediately What went wrong? Sometimes, RTCPeerConnection.close() will hang for a short period of time, affecting the entire tab. Did this work before? Yes 60.0.3112.90 Does this work in other browsers? Yes Chrome version: 60.0.3112.101 Channel: stable OS Version: 10.0 Flash Version:
,
Aug 24 2017
,
Aug 24 2017
james@: Can you reproduce this issue in Chrome 61 (currently Beta) or 62 (currently Dev/Canary)? From your report it looks like this was not reproducible on 60.0.3112.90, but is reproducible on 60.0.3112.101. However, there aren't changes that should have impacted RTCPeerConnection performance between those two releases.
,
Aug 24 2017
Yes, I will try 62/Canary. However, I'm on vacation currently. I get back Sept 4th. I'm reasonably certain the change happened between 90 and 101. I'm currently developing an RTC app so I'm continuously using the RTC APIs, and the hang suddenly started happening after Chrome updated. I do have a workaround (to call close() via a setTimeout after 30s) James
,
Aug 24 2017
Thank you for providing more feedback. Adding requester "guidou@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 4 2017
guidou@: The problem seems to be resolved in 62.
,
Sep 4 2017
Closing as per #6 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Aug 18 2017