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

Issue 778855 link

Starred by 3 users
Status: Fixed
Owner:
m...@chromium.org
Closed: Dec 18
Cc:
█ gyzhou@chromium.org
guidou@chromium.org
niklase@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug

Blocked on:
issue 754872


Sign in to add a comment

[Desktop Capture] Chrome can't share its own window by window capture on Win7

Project Member Reported by braveyao@chromium.org, Oct 26 2017 
Chrome Version: all
OS: Win7

What steps will reproduce the problem?
(1) Launch Chrome, Stable or Canary, on Win7.
(2) Start desktop capture, by Hangout or sample extension
(3) Choose its own window in "Application Window" tab

What is the expected result?
window starts to share

What happens instead?
no captured window image

Please use labels and text to provide additional information.
Chrome can share its own window on other platforms, Win10/Linux/OSX.
This should works before on win7 too. No idea when it's broken.

Track down the codes with following findings:

- The aura window capture fails to get gl_helper_,  https://cs.chromium.org/chromium/src/content/browser/media/capture/aura_window_capture_machine.cc?l=327.
- Because GpuProcessTransportFactory::GetGLHelper() can't get the context provider, https://cs.chromium.org/chromium/src/content/browser/compositor/gpu_process_transport_factory.cc?l=902.
- And the final reason is GpuDataManage can't use swift_shader for GpuBrowserCompositor, https://cs.chromium.org/chromium/src/content/browser/gpu/gpu_data_manager_impl_private.cc?l=969.

Comment 1 by braveyao@chromium.org, Oct 26 2017

Owner: m...@chromium.org
Status: Assigned (was: Untriaged)
Hi miu@, I'm not familiar with the aura implementation and related GPU supports. Could you please have a check for appropriate triage? Thanks!

Comment 3 by braveyao@chromium.org, Oct 27 2017 

IIRC, when I closed  issue726664 , this worked with Canary. But soon broken again. So I filed this one.

Taking a closer look, it seems that on Win7 swift_shader is preferred and gpu::GPU_FEATURE_TYPE_GPU_COMPOSITING is blacklisted on my Win7 box. So AuraWindowCaptureMachine can't work because GpuDataManagerImplPrivate::CanUseGpuBrowserCompositor() returns false, https://cs.chromium.org/chromium/src/content/browser/gpu/gpu_data_manager_impl_private.cc?l=964. Wondering if it's related to the HW config?

So the question is how to do aura window capture under this situation?

Comment 4 by niklase@chromium.org, Oct 27 2017

Cc: gyzhou@chromium.org

Comment 5 by m...@chromium.org, Oct 27 2017 

re #3: That shouldn't matter. If the GPU compositing is disabled, the browser will automatically fall-back on software compositing.

FWIW, it's probably not worth spending much time on this bug. In a couple weeks, tab/desktop/window capture will be moved into VIZ, all sharing a common implementation. See  bug 754872 .

Comment 6 by braveyao@chromium.org, Oct 27 2017 

Good to know! Thanks miu@ for the update!
Will revisit when it happens then.

Comment 7 by m...@chromium.org, Jan 25 2018

Blockedon: 754872

Comment 8 by m...@chromium.org, Dec 18

Status: Fixed (was: Assigned)
►

Sign in to add a comment