Full-screen capture: Wallpaper or other background flickers in and out |
|
Issue descriptionChrome Version: 55.0.2883.87 OS: Win10 What steps will reproduce the problem? (1) Using a screen sharing extension such as CrankWheel, share full screen on Win10 machine What is the expected result? The screen should be shared as-is. What happens instead? In some frames, the screen share looks good. In others, we see the desktop wallpaper or other bits of the background (sometimes wallpaper and desktop icons) instead of parts (or sometimes all) of the foreground window(s). This was reported to us by a customer of CrankWheel, he was using an Acer laptop with Win10 installed. I'm not sure whether or not he had Aero turned on or not, but I could check with him again if you believe it might make a difference. We attempted to reproduce and so far have been able to reproduce on a BrowserStack (https://www.browserstack.com/) virtual machine running Windows 10. See video of our repro here: https://www.dropbox.com/s/5iat0dcvml9zjnz/screenCapture.mov?dl=0 Assigning to niklase@ as this seems like it might possibly be related to issue 496110 or issue 466879 . I didn't think to check the about:gpu page but will ask the customer and also try this on our repro scenario and paste the details in comments below.
,
Jan 4 2017
We're in the process of replacing the current capturer for Windows, if possible it would be great to know if the problem goes away by --enable-features=DirectXScreenCapturer
,
Jan 5 2017
Sorry for the late response here. I've asked the user this reproduces for to test with the command line, and also to send the about:gpu details from his machine. Will post back when I have an answer.
,
Jan 5 2017
Forgot to say: I can't set flags for Chrome on the BrowserStack machine where this reproduces, or I would do that. On other virtual machines we've tried, and on the Windows hardware we have access to, it does not reproduce.
,
Jan 13 2017
OK, finally, I've been able to walk through the steps of adding --enable-features=DirectXScreenCapturer with the user where the issue reproduces.
Unfortunately, the issue still reproduces with the --enable-features=DirectXScreenCapturer flag added.
I verified that the command line looks right in the browser where they tested ("C:\Program Files (x86)\Google\Chrome/Application\chrome.exe" --enable-features=DirectXScreenCapturer --flag-switches-begin --flag-switches-end).
|
|
►
Sign in to add a comment |
|
Comment 1 by joi@chromium.org
, Jan 4 2017