New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 633802 link

Starred by 3 users

Issue metadata

Status: Verified
Owner:
Last visit > 30 days ago
Closed: Sep 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 3
Type: Bug



Sign in to add a comment

Move ScreenCapturer Differ logic out of each implementation

Project Member Reported by zijiehe@chromium.org, Aug 3 2016

Issue description

This is a work item to track all the changes to move ScreenCapturer Differ logic out of each implementation.

As most of the ScreenCapturer implementations need to compare the changes of two frames and set the DesktopFrame::updated_region(). It would be better to have an individual layer to handle the Differ logic.
 
Status: Assigned (was: Untriaged)
Project Member

Comment 2 by bugdroid1@chromium.org, Sep 25 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/3ba38ac9d3ae2b0d1d4d5230cd1280d417694390

commit 3ba38ac9d3ae2b0d1d4d5230cd1280d417694390
Author: zijiehe <zijiehe@chromium.org>
Date: Sun Sep 25 20:12:26 2016

[Chromoting] Use detect_updated_region option in remoting

ScreenCapturer / DesktopCapturer do not always need to detect more accurate
updated region, since some consumers do not really care about the updated
region. And according to the analysis, a Differ call may use some 10 ms for a
2560 x 1440 DesktopFrame. So Differ logic will eventually be moved out of
ScreenCapturer / DesktopCapturer implementations.
But a more accurate updated region is useful for Chromoting, since we do not
need to send an unchanged frame to the client. So this change actively sets
detect_updated_region in DesktopCapturerOptions to ensure
ScreenCapturerDifferWrapper is used.

This change will be submitted together with WebRTC change
https://codereview.chromium.org/2348803003/ to avoid the differ to be involved
twice.

BUG= 633802 

Review-Url: https://codereview.chromium.org/2348943002
Cr-Commit-Position: refs/heads/master@{#420863}

[modify] https://crrev.com/3ba38ac9d3ae2b0d1d4d5230cd1280d417694390/remoting/host/basic_desktop_environment.cc

Owner: ajnolley@chromium.org
Status: Fixed (was: Assigned)
After WebRTC changes https://codereview.chromium.org/2314323002/ & https://codereview.chromium.org/2348803003/ and the Chromium one above, the required changes are all submitted.

Resolved as fixed.

AJ, just FYI. This change should have no logic impact to chromoting.
Status: Verified (was: Fixed)
I ran through P0 tests on ToT, as part of my weekly tests. I found no regressions, so this should be good. Verified in 55.0.2873.0 web app and host. 

Sign in to add a comment