AuraDesktopCapturer is slow |
|||||||||
Issue descriptionRepro steps: Connect It2Me to a chromebook. Expected: Low CPU consumption, system is still usable. Observed: Browser process consumes almost 2 cores. The problem is that the capturer uses RequestCopyOfOutput() API to capture the screen. So we end up capturing the whole screen, converting it to RGB and passing it whole to the encoder up to 30 times per second. It should be possible to fix this problem by using media::ScreenCaptureDeviceCore, which is much more efficient - it only captures the screen when it changes (it's the same mechanism that's used for chromecast).
,
Apr 19 2016
Sure. Will take a look
,
Apr 28 2016
Looks like the magic of printing only when necessary is done by AuraWindowCaptureMachine instead of ScreenCaptureDeviceCore. It implements ui::CompositorObserver and calls RequestCopyOfOutput() only when OnCompositingEnded is triggered.
,
Apr 28 2016
The OnCompositingEnded interface they used wasn't very reliable and they have changed to use OnAnimationStep. http://crbug.com/492839 I'll try to implement a new capturer using the logic they have and see how well it works.
,
May 12 2016
Please see bug 607272 . That's a proposed long-term solution to fix this issue. You may just want to mark this bug as a duplicate of that one.
,
May 12 2016
,
May 12 2016
We are currently not using AuraWindowCaptureMachine and may not be able to easily reuse that. I'll keep an eye on the changes to the compositor subscriber.
,
Jun 1 2016
Moving this nonessential bug to the next milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jul 13 2016
This issue has been moved once and is lower than Pri-1. Removing the milestone. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 17 2017
,
Nov 17 2017
,
Nov 18 2017
,
Nov 19
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Nov 19
This has long been fixed (impl replacement, see bug 754872 and linked bugs from there). :) |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by jamiewa...@chromium.org
, Apr 19 2016Labels: M-52
Owner: yuweih@chromium.org
Status: Assigned (was: Untriaged)