Issue metadata
Sign in to add a comment
|
Local build of chrome.exe paints windows all black, unless launched with --disable-gpu |
||||||||||||||||||||||
Issue descriptionThe high level symptom is very similar to issue 781642 and issue 780498 : When I launch chrome.exe the window is all black. My case is a bit different in that it happens specifically just for builds of chrome.exe that I have made. * I can successfully launch the Stable channel of Chrome * I can successfully launch builds off the continuous builder * Running chrome.exe which I have built fails with all black windows; running ith with --disable-gpu resolves the issue. My development environment is a freshly installed Windows 10, chromium checkout, and using the depot_tools windows toolchain. AFAIK I am using all the default settings.
,
Dec 13 2017
,
Dec 13 2017
My source checkout is revision 93b9f9ceeeae60e97105de9e4cacc809b06d08ab. I have tried a variety of gn.args combinations but the build products all behave the same way: is_debug = false use_goma = (I have tried both) is_component_build = (I have tried both) enable_nacl = (I have tried both)
,
Dec 13 2017
,
Dec 13 2017
Can confirm, my canary build refuses to launch as anything other than a black screen for the last 2 days, so unable to use the built in bug reporting tool. Win10 64 bit NVidia gtx 970 newest driver release.
,
Dec 13 2017
If I use --disable-gpu Will I need to reenable the gpu at a later date?
,
Dec 13 2017
,
Dec 13 2017
For me the issue is specific to my local build - both the Canary channel (65.0.3293.0) and ToT builds from continuous builder work. I will try building at different revisions and see if it is related to a code change, in case I simply got unlucky with my checkout version. But my case may still be interesting for debugging the black window issue (any Google developers in MTV are free to debug on my machine), and understanding how to make that failure mode better. Thanks!
,
Dec 13 2017
Upgrading to P1 – this failure mode sounds potentially urgent. Will work with eroman@ to try to figure out whether this is related to code paths like DirectComposition.
,
Dec 14 2017
It looks like this was caught by the Win10 GPU bots. Unfortunately they're FYI-only currently. Good -> bad transition yesterday: https://ci.chromium.org/buildbot/chromium.gpu.fyi/Win10%20Release%20%28NVIDIA%29/4220 https://ci.chromium.org/buildbot/chromium.gpu.fyi/Win10%20Release%20%28NVIDIA%29/4221 It was fixed again later in the day yesterday: https://ci.chromium.org/buildbot/chromium.gpu.fyi/Win10%20Release%20%28NVIDIA%29/4229 https://ci.chromium.org/buildbot/chromium.gpu.fyi/Win10%20Release%20%28NVIDIA%29/4230 We need to complete the switchover of the GPU bot fleet to primarily Windows 10 in Issue 711839. However there's a blocking task on that one to allow our Swarming tasks to dynamically select one of two (or N) different configurations.
,
Dec 14 2017
This was probably the CLs landed and reverted in angleproject:1649. We should still work on converting the majority of the test machines to Windows 10. Closing this one as WontFix though.
,
Dec 14 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by eroman@chromium.org
, Dec 13 20175.5 KB
5.5 KB View Download