New issue
Advanced search Search tips

Issue 638971 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

getUserMedia fails to properly share applications like Dota 2

Reported by doak.m...@gmail.com, Aug 18 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36

Steps to reproduce the problem:
1. Open Dota 2
2. Open Google Hangouts
3. Share screen and select Dota 2 as the source

What is the expected behavior?
Should share a stream of Dota 2 just as any typical screen sharing session would.

What went wrong?
The screen share renders the first frame of Dota 2 after it has loaded and doesn't render any new frames. However, the stream isn't actually frozen because you can see the mouse cursor in Dota 2 moving.

https://drive.google.com/file/d/0B0DTRJTEH3FHdVdIcWczd3ZXLVk/view

This shows the images we capture from a computer that was not working as expected. I have confirmed that it is a problem with the stream we receive by displaying a video of the Dota 2 stream and Entire Screen (Screen 1) stream side by side -- showing that the Dota 2 stream did not work but the full screen did. I do not have the video of this but can record one if necessary.

Did this work before? N/A 

Chrome version: 52.0.2743.116  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 22.0 r0

About a fourth of our users experience this issue. We use Electron to capture Dota 2 with getUserMedia to process the current state and provide statistics.

Unfortunately users that experience this issue have the same version as those who do not experience this. We have been unable to identify the difference in setup between those who have it working and those who don't.

Steam forces Dota 2 to stay up to date so the version of that should be the same as well.
 

Comment 1 by ajha@chromium.org, Aug 25 2016

Components: Blink>GetUserMedia
Labels: Needs-Feedback
[triage] Could this be a limitation of the API used in Windows for capturing the screen? Maybe it doesn't handle D3D based games? 

doak.matt@ Do you have other Direct3D based games you could try? And maybe openGL as well? You can apparently run Dota 2 using openGL by adding "-gl" as start param in steam for the game.

Comment 3 by doak.m...@gmail.com, Aug 30 2016

Can confirm running Dota 2 with OpenGL causes the issue.

Running with -vulkan has different issues. When the game isn't in focus it shows the windows underneath instead of properly capturing Dota as it does normally.

Only the default mode (I guess that's Direct3d?) works as intended.


Project Member

Comment 4 by sheriffbot@chromium.org, Sep 7 2016

Labels: -Needs-Feedback Needs-Review
Owner: jansson@chromium.org
Thank you for providing more feedback. Adding requester "jansson@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: sergeyu@chromium.org niklase@chromium.org jansson@chromium.org
Components: -Blink>GetUserMedia Blink>GetUserMedia>Desktop
Owner: ----
Status: Available (was: Unconfirmed)
sergeyu@, niklase@ do you have any input here?

Comment 6 by cda...@chromium.org, Mar 13 2017

Labels: -Needs-Review
Cleaning up "Needs-Review" label as we are not using this label for triage anymore. Ref bug for this cleanup 684919
Project Member

Comment 7 by sheriffbot@chromium.org, Apr 12 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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
Status: WontFix (was: Untriaged)
The capturer has been completely rewritten, reopen if this is still an issue.

Sign in to add a comment