Black rendered window when Nvidia 940MX set as default graphics in dual gpu config Windows 10
Reported by
j...@opera.com,
May 24 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.81 Safari/537.36 OPR/45.0.2552.812 Steps to reproduce the problem: 1. Need to have dual gpu configuration, Intel + NVidia 2. Go to Nvidia control panel, in 3D settings set prefered graphics processor th "High-performance NVIDIA processor" 3. Run Chrome What is the expected behavior? Properly rendered Chrome window What went wrong? Black window, nothing visible, but clicking on default button places seems to work, e.g. close, maximize etc. NOT reproducible on Windows 7 Did this work before? No Chrome version: 60.0.3109.0 Channel: canary OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 25.0 r0 Configuration: Lenovo ThinkPad T460p, Intel HD Graphics 530 + NVidia GPU 940MX. After more ivestigation I see that Chrome's gpu process runs on Windows 7 system with --disable-direct-composition switch. On Windows 10 system without it. After adding switch and run Chrome everything is rendered properly.
,
May 25 2017
,
May 25 2017
Don't have dual gpu set up on any of the Windows machine available as of now. Looping MTV team and adding respective component for help in further triaging of this.
,
May 26 2017
#0: Can you describe your setup in more detail? What output is connected to the display (intel or nvidia) and if you're using multiple displays?
,
May 26 2017
Also try testing an older version of Chromium: https://www.googleapis.com/download/storage/v1/b/chromium-browser-snapshots/o/Win%2F444943%2Fchrome-win32.zip?generation=1484879768408272&alt=media (that's the build that was used as the base for M57)
,
May 30 2017
Thanks for the build :) I've checked that and It's reproducible. I have only one build-in display with maximum resolution 1920 x 1080. No external displays attached.
,
Jun 26 2017
,
Aug 16 2017
,
Aug 20
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
,
Aug 24
zmo, can you triage this?
,
Aug 24
jryc@opera.com: do you still have this issue? My educated guess would be Chrome mistakenly thinks it's still running on Intel and using Intel GPU settings while it's actually running on NVIDIA, thus going down a wrong path as far as direct composition is concerned. |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by j...@opera.com
, May 24 201712.2 KB
12.2 KB View Download