WebRTC screen sharing crashes when the text resolution is set to the recommended value 150%
Reported by
arnaud.b...@symphony.com,
May 6 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/50.0.2661.94 Safari/537.36 Steps to reproduce the problem: 1. Goto to any project that leverages WebRTC screen sharing (https://meet.jit.si , https://www.webrtc-experiment.com/Pluginfree-Screen-Sharing/ ...) 2. install the required extension 3. click on the icon to share your screen 4. select the first option to share your entire screen 5. click on "Share" 6. complete crash of the browser What is the expected behavior? What went wrong? getUserMedia error: "gum.unsupported_resolution" Crashed report ID: d1300a7200000000 (3baf68d0-4888-423c-8284-dcf8d395f76d) How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? No Chrome version: 50.0.2661.94 Channel: stable OS Version: Windows 10 Pro Flash Version: Shockwave Flash 21.0 r0
,
May 7 2016
I have cleared (deleted) all my google chrome extensions and retested without any. Chrome browser systematically crashes. As soon as i put my resolution of fonts to 100% - it works perfectly.
,
May 7 2016
Windows 10 Pro, not 7, and deleted all the extensions then restarted Chrome to make sure there is not side effect. My guess is that the resolution is awkward because of this option, and this makes getusermedia crash. Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.
,
May 7 2016
Re #3: I don't have the means to test on Windows 10 Pro at this time, but it sounds like that shouldn't matter. Can you please verify this on Canary version (52.0.2727.0)?
,
May 19 2016
Stack trace of this matches to that Issue 513140, hence merging into that.
,
Jun 22 2016
I don't have access to the Issue 513140, could you guys please help me on this?
,
Oct 10 2016
Hi, I was wondering if there's been any update on this. I'm still seeing the issue and was wondering where the investigation and resolution is at for this behavior as its been some time with no fresh news. Thanks! |
||
►
Sign in to add a comment |
||
Comment 1 by chromium...@gmail.com
, May 7 2016