Issue metadata
Sign in to add a comment
|
No Remote party video or audio on Windows 10 OS for a Window to Linux Ubuntu (14.04) AppRTC H264 call |
||||||||||||||||||||||
Issue descriptionChrome version: 58.0.3029.6 / Dev Operating System: Windows 10 What steps will reproduce the problem? 1. Browse to https://appr.tc/?vsc=h264 on a windows 10 machine, open a javascript console and enter a room name 2. Browse to https://appr.tc/?vsc=h264 linux Ubuntu (14.04) machine, open a javascript console and enter the room name from step 1 What happens instead? Step 2: -- Audio and Video flows between the appRTC call users -- Local party (Windows): sees remote party (Linux) video, hears remote party audio -- Remote party (Linux): sees local party (Windows) video, hears local party audio -- Both local and remote party sees their own camera video in the selfview icon (bottom left hand corner), -- Both local and remote party see call control icons (including "hangup" icon) when the appRTC call is in progress Actual results Step 2: -- Local party (Windows): does not see remote party (Linux) video, does not hear remote party audio -- Local party (Windows): no selfview camera video icon (bottom right) -- Local party (Windows): the "hangup” icon is missing -- Remote party (Linux): has no issues Please provide any additional information below: The bug is NOT seen between Window 10 amd MacOS (10.12.3) The bug is also seen between MacOS (10.12.3) and Linux (Ubuntu 14.04) It doesn't matter who initiates the appRTC call i.e Windows or Linux the bug is still seen. The bug is NOT seen when forcing video codec VP8 (or VP9) eg https://appr.tc/?vsc=vp8 No Java Script errors are seen Bisecting gives the following info: You are probably looking for a change made after 433822 (known good), but no later than 433828 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/3ae9c46897ad5b00cfa684f1d5120c5b6a676808..c2564bc627cb950b124ac8e41bc5fd3187f7ad9c
,
Mar 15 2017
Possible suspect - https://chromium.googlesource.com/chromium/src/+/2ef345ec6181043befdf522306225453500397ef Assigning to reviewer. Even though this was an old regression, we can take the fix for the current Milestone, hence adding an RB label.
,
Mar 16 2017
Magnus - could this be related to https://chromium.googlesource.com/chromium/src/+/c2564bc627cb950b124ac8e41bc5fd3187f7ad9c ?
,
Mar 17 2017
My revert (https://chromium.googlesource.com/chromium/src/+/c2564bc627cb950b124ac8e41bc5fd3187f7ad9c) looks very suspicious because it's related to H264, but the CL that was reverted was landed less than 24 hours before that, so this issue should be present before the original CL (https://crrev.com/510eddede44cb4b67c8f17fdd68cefb780a668c5) as well then. jkallar@ - Is this something you can test?
,
Mar 17 2017
This issue is tagged as RB- Stable , please try to resolve ASAP.
,
Mar 17 2017
I'm OOO for a week, so please re-assign then.
,
Mar 28 2017
magled@: I do NOT find the fault in this bug when tested in the previous version (57.0.2925.0) Original CL (https://crrev.com/510eddede44cb4b67c8f17fdd68cefb780a668c5) = 57.0.2928.0 (Nov 21) Previous version before CL (https://crrev.com/90e19ba1edc164e34f2be6e258f1dc1cd4962740) = 57.0.2925.0 (Nov 19)
,
Apr 3 2017
jkallar@ Can you please test in latest M58 Beta and update the thread. https://www.google.com/chrome/browser/beta.html. If the issue still exist we need to fix ASAP since M58 is almost close to stable.
,
Apr 4 2017
ligimole@> I DON'T any more get the fault with Chrome Beta (58.0.3029.41) doing a AppRTC h264 call between Windows 10 and Linux (Ubuntu 14.04) I'll hence changed state to: Verified.
,
Apr 4 2017
[Auto-generated comment by a script] We noticed that this issue is targeted for M-58; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-58 label, otherwise remove Merge-TBD label. Thanks.
,
Apr 4 2017
Great Thanks. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ligim...@chromium.org
, Mar 15 2017