Issue metadata
Sign in to add a comment
|
Hangouts shares wrong screen
Reported by
contraba...@gmail.com,
Jun 29 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.2; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: In Hangouts, I have a two monitor configuration and when I select a screen to share, suddenly with the new release it shares the wrong screen. It's been working fine for a couple of years. What is the expected behavior? It should share the screen I asked it to share, not the other one or throw an error. What went wrong? If I click to share "Screen 1", it shares Screen 2. If I click to share "Screen 2", when I click Share it pops up "Error: Sorry, an error has occurred when screensharing. CLOSE." I doubt it makes a difference, but the left monitor (monitor 2) is vertical and the right monitor (monitor 1) is horizontal. This bug seems to have cropped up around the release of Chrome Version 59.0.3071.104 Did this work before? Yes The revision before 59.0.3071.104 Chrome version: 59.0.3071.115 Channel: stable OS Version: 6.2 (Windows 8) Flash Version: Shockwave Flash 26.0 r0
,
Jul 18 2017
To add some more information to this, while I also experience similar problems using Chrome 60.0.3112.66 on Windows 10 (15063.483), I've also had problems where just opening the Hangouts screenshare page causes Chrome to close. This is a full closure of all tabs and all windows across multiple profiles. In the past, I've been able to avoid a crash by selecting the lower indexed screens and accepting that they will share a different monitor, but it now crashes before it reaches this point. This problem has been present for several months now across multiple Windows builds and multiple Chrome versions in varying forms. In case anyone wants to hunt out my crash dump, it's here: Crash ID: crash/c88c703c88000000
,
Jul 28 2017
Thanks For filing the issue! Tested in chrome # 59.0.3071.115 and Canary #62.0.3169.0 on win 10.0 and not able to reproduce the issue. @ rcalvanese / daernsinstantfortress: As per provided crash id(c88c703c88000000) checked in crash server it is fixed in after - #61.0.3159.0 Could you please create new profile without extensions and apps.Re-check once and let us know the observations of the issue which would help us to triage the issue further. Note: Ref issue 741252 Thanks in Advance.
,
Sep 1 2017
,
Sep 8 2017
Zijiehe, this is a dupe of something already fixed, right?
,
Sep 8 2017
Yes, this has been fixed for a while. The root cause and related changes are in bug https://bugs.chromium.org/p/chromium/issues/detail?id=732224.
,
Sep 8 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by rcalvan...@gmail.com
, Jul 3 2017