Issue metadata
Sign in to add a comment
|
native dialog blocks video play and RTCPeerConnection video sending
Reported by
kan...@vcube.co.jp,
Sep 28 2016
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:49.0) Gecko/20100101 Firefox/49.0 Example URL: https://appear.in Steps to reproduce the problem: 1. Join the same room in https://appear.in with 2 browsers: A (chrome) and B (firefox) 2. Wait until A and B can see video from each other 3. In browser A: type `javascript:alert()` in URL bar What is the expected behavior? All 4 Videos in browser A/B continues playing. What went wrong? 3 videos are paused: 2 videos in browser A, and remote video (from A) in browser B. These 3 videos continues to play if alert dialog in A is dismissed. Did this work before? N/A Chrome version: 53.0.2785.116 (64-bit) Channel: stable OS Version: OS X 10.11 Flash Version: Shockwave Flash 23.0 r0
,
Sep 28 2016
I believe alert() pauses Javascript execution until the dialog is dismissed, so this is probably expected behavior. Regardless, not a network problem.
,
Sep 29 2016
In this case remote video in B (and some underlying stuff I presume?) is also blocked. Not really sure if this can be a potential problem.
,
Sep 30 2016
Not related to V8.
,
Sep 30 2016
Tested in chrome stable #53.0.2785.143 and canary #55.0.2876.0n Mac 10.12 able to reproduce the issue. Below are the Bisect Details: Bisect Info: ============= Good Build: 52.0.2742.0(394842) Bad Build: 52.0.02743.0(394939) Bisect URL: =========== You are probably looking for a change made after 394860 (known good), but no later than 394886 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/6b693cb69c1731ac3e4fa0851e64fd10fa820a1c..003cd61ab7a3e38d8f7fdfe55068c5450ed1bb68 Unable to find a possible suspect from the CL generated. Untriaging it so that it gets addressed. Note : Unable to test the issue on linux OS as there is no cam available and in windows only user can see one video at a time per browser.
,
Sep 30 2016
The alert and other promoting dialogs pause event execution by design. The remote video in B stops because Chrome also stops sending data - the event loop is paused. We will not change this behavior. Giving scheduling component because I don't know what else to use for event processing. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by kan...@vcube.co.jp
, Sep 28 2016