[Chromoting] Setting a small x-google-min-bitrate causes lag when bandwidth estimator gives us unreasonable value |
||||||
Issue descriptionThis is a chromoting specific issue. The change has been submitted by change https://chromium-review.googlesource.com/c/chromium/src/+/749921 This change requires to be merged to M63. It impacts only Chromoting, so we do not need to verify it on canary.
,
Nov 1 2017
This bug requires manual review: M63 has already been promoted to the beta branch, so this requires manual review Please contact the milestone owner if you have questions. Owners: cmasso@(Android), cmasso@(iOS), gkihumba@(ChromeOS), govind@(Desktop) For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 1 2017
To make it very clear, this change is in //remoting folder, it won't affect Chrome by any means.
,
Nov 1 2017
Approving merge to M63 branch 3239 per comment #3 and per offline chat with zijiehe@, this impacts only Chromoting, won't affect Chrome at all and safe to merge. Please merge ASAP. Thank you.
,
Nov 3 2017
,
Nov 3 2017
Please merge your change M63 branch 3239 by 4:00 PM PT Monday (11/06/17) so we can take it for next week Beta release. Thank you.
,
Nov 3 2017
Sorry, the commit is logged at https://bugs.chromium.org/p/chromium/issues/detail?id=769391#c75. This change has been merged already. Update the labels.
,
Nov 3 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by zijiehe@chromium.org
, Nov 1 2017