Issue metadata
Sign in to add a comment
|
Regression: Video gets stuck and weird traces are seen on doing hangouts video call when color enhancer extension is present |
||||||||||||||||||||||
Issue descriptionVersion : 55.0.2858.0 Platform: 8799.0.0 Devices : Daisy,Peppy and Gnawty OS : Chrome OS Test URL: https://chrome.google.com/webstore/detail/color-enhancer/ipkjmjaledkapilfdigkgfmpekpfnkih?utm_source=chrome-app-launcher-info-dialog What steps will reproduce the problem? (1) Sign in to user >> Add above extension and try doing hangouts video call. Expected: Should be able to do video call without any struck. Actual: Instead hangouts video call gets stuck and weird traces of video is seen. This is a regression issue as same is working fine in 53.0.2785.103/8530.81.0 stable channel daisy. Issue is also seen in 54.0.2840.24/8743.25.0 dev channel blaze.
,
Sep 16 2016
Seems unlikely this is an extensions platform issue.
,
Sep 26 2016
as per bug opener, issue happens when make hangout video call. give to WebRTC team
,
Sep 30 2016
srcv@: can you confirm this behavior? sc00335628@techmahindra.com: I'm not sure we can entirely blame Chrome for the regression. It might also be that the Web Platform APIs or behavior has changed since M53 so they extension needs to be updated. Are you able to produce any more detailed logs that showcases why the "video call gets stuck and weird traces of video is seen." ?
,
Sep 30 2016
I was able to reproduce this issue on chrome device Peppy with M54 54.0.2840.43 / 8743.44.0 beta. Gcomm hangout: - Add 'Color enhancer' extension and start a hangout call - Click on 'Invite people' - Hangout screen gets stuck as soon as dialog box for sending invite opens up (mouse cursor movements were allowed) Hotlane: - Add 'Color enhancer' extension and start a hangout call - Hangout receiving video was stuck in between and displayed overlapped video frames (sometimes) Note: 1. This issue is not observed during apprtc calls on Peppy with M54 2. This issue is not observed during hangouts on device Peppy with M53 stable (53.0.2785.144 / 8530.93.0) 3. Please find attached hangout webrtc-internal dump from device Peppy with M54 beta
,
Oct 3 2016
Assigning Blink>WebRTC>Video component for further triage.
,
Oct 18 2016
It didn't make it into M55 so moving to M56.
,
Nov 15 2016
Bumping to M57. Please update if that's wrong. Is this a Pri 1?
,
Jan 23 2017
Bumping this to M58. Please correct if that's wrong.
,
Mar 9 2017
Niklas - Can you triage?
,
Mar 9 2017
Since this is a Google extension I'll try to find the authors and discuss it with them.
,
Mar 9 2017
btw, this can't be a p2 since it's easy to disable the extension.
,
Mar 9 2017
+kevers@ in case he has bandwidth to work on the extension.
,
Mar 9 2017
+dmazzoni@, word on the street says you might know something about this.
,
Mar 15 2017
,
Mar 15 2017
@dmazzoni - Please update bug with bisect info. Thanks!
,
Mar 23 2017
This is related to issue 701521 but since it is video, possibly caused by a different bug. +senorblanco@ in case it is the same root Blink invalidation bug.
,
Apr 24 2017
Bumping to M60. Please correct if that's wrong.
,
Apr 24 2017
Our latest build should have fixed this, maybe someone can verify?
,
Apr 24 2017
I could not reproduce this issue on Chrome OS device Peppy with M59 59.0.3071.15 / 9460.5.0 dev
,
May 5 2017
srcv, wnwen, should we mark this as fixed?
,
May 8 2017
,
Jun 2 2017
,
Aug 1 2017
,
Jan 22 2018
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ajha@chromium.org
, Sep 14 2016Status: Untriaged (was: Unconfirmed)