WebRTC screen share source selection errors and crashes related to resolution change
Reported by
skadb...@cyviz.com,
Nov 24 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:56.0) Gecko/20100101 Firefox/56.0 Steps to reproduce the problem: 1. Start Chrome 2. Apply a desktop resolution change 3. Select a screen source, start sharing using chrome.desktopCapture.chooseDesktopMedia What is the expected behavior? Once a video source has been selected, the API will successfully return a valid video stream What went wrong? a. The entire Chrome browser crashes b. The tab crashes c. "Screen 1" was selected, but "Screen 2" is returned as the selected stream. d. "Screen 1" was selected, displaying the contents of "Screen 1", but without the cursor. However when the cursor is present on "Screen 2", it is drawn in the video stream as if on "Screen 1". Error outcome a) is rare. When browser crash is avoided, the errors b,c,d) are reproduceable until the Chrome browser is restarted. For example, in a 3 monitor setup, it has been observed when selecting "Screen 1", "Screen 2" is shown. When selecting "Screen 2", "Screen 3" is shown. Finally when "Screen 3" is selected, the tab crashes. Did this work before? No Does this work in other browsers? N/A Chrome version: 62.0.3202.89 or earlier Channel: stable OS Version: 10.0 Flash Version: N/A These issues have been reported on multiple systems, but mainly laptops with docking capability and external screens. Restarting the Chrome browser fixes the issue. I'll note that I've had similar issues in a win32 application where invalid HDC handles were used. Potentially related issue: https://bugs.chromium.org/p/chromium/issues/detail?id=764258
,
Nov 27 2017
The issue seems to be related to dual monitor. Hence, adding label TE-NeedsTriageFromHYD and requesting someone from inhouse to take a look into the issue. Thanks...!!
,
Nov 29 2017
Unable to reproduce the issue on Win-10 and Win-7 dual monitor set up using chrome reported version #62.0.3202.89 and latest stable #62.0.3202.94 Following are the steps followed to reproduce the issue. ------------ 1. Started Chrome 2. Applied a desktop resolution change 3. Shared screen using a screen share by adding extension form the link: https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fgooglearchive%2Fchrome-app-samples%2Ftree%2Fmaster%2Fsamples%2Fdesktop-capture&sa=D&sntz=1&usg=AFQjCNHbmmCMEYEa3l8NDqiWW_x-S5lOFw. 4. Observed that the chrome did not crash and "Screen 1" was selected, and in return screen 1 only is returned as the selected stream. skadberg@ - Could you please provide the crash id from chrome://crashes for further triaging from TE-end. ccing zijiehe@ from the issue https://bugs.chromium.org/p/chromium/issues/detail?id=764258 as a reference. Thanks...!!
,
Nov 29 2017
The issue occurred less than ten times during a 12 month period. The last occurrence must have been around July (v59?) this year. I assumed that I was still running an outdated Chrome version, but it appears that my browser has forcefully updated itself. I was unable to reproduce the problem with the most recent version, but I went back to v56.0.2924.87 and was able to crash the browser at random, please see the attached crash dump.
,
Nov 29 2017
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 4 2017
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by guidou@chromium.org
, Nov 24 2017