Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Electron apps entirely blank after updating to Windows 10 build 16257.1 #10239

Closed
Pokechu22 opened this issue Aug 10, 2017 · 13 comments
Closed

Comments

@Pokechu22
Copy link

All electron apps are blank for me after updating Windows 10 to the latest preview build (10.0.16257.1). This has persisted after several restarts, and affects production apps (tested with slack and discord).

  • Electron version: 1.7.5
  • Operating system: Windows 10 insider preview build 10.0.16257.1

Expected behavior

Apps would not be entirely blank (as was the case on windows build 10.0.15065).

Actual behavior

Apps are completely blank, including the quick-start app (no modifications; this is just running it directly):

electronblank

How to reproduce

I'm not 100% sure if this will be consistent to reproduce, or only will happen on my machine.

The only step that I can provide is updating to the latest Windows insider preview build (10.0.16257.1), and then launching any electron app (I used the sample given in the quick start section).

If there's more information I can provide, let me know.

@bpasero
Copy link
Contributor

bpasero commented Aug 12, 2017

@Pokechu22 does this reproduce with Electron 1.6.x too?

@Pokechu22
Copy link
Author

Tried 1.6.2; same problem as 1.7.5.

@bpasero
Copy link
Contributor

bpasero commented Aug 12, 2017

@Pokechu22 any output printed to the chrome developer console?

@Pokechu22
Copy link
Author

I don't know how to open the developer console; if the View → Toggle Developer Tools button is supposed to open it, that is blank as well, although it does make the app black instead of white (which changes back after toggling again):

electronstillblank

There's nothing of note in the command window:

C:\Users\Pokechu22\Downloads\electron-quick-start>npm start

> electron-quick-start@1.0.0 start C:\Users\Pokechu22\Downloads\electron-quick-start
> electron .



C:\Users\Pokechu22\Downloads\electron-quick-start>

I checked my pi to see what it should look like, and tried to switch to the console tab by clicking near the middle top. As far as I can tell, there's nothing in the console, since I can select it and copy from there and there's no results (as a control, I typed in test and then tried again, and I successfully copied a Uncaught ReferenceError message, so I think I can actually select).

@kristaps-ancans
Copy link

Issue persists on Windows 10 insider preview build 16299.19.

Affected applications - VS Code (doesn't matter which version), GeForce Experience.

@jarek-foksa
Copy link

Have you tried launching the app with hardware acceleration disabled? This can be done with --disable-gpu command line flag or by calling app.disableHardwareAcceleration() in the main process before the app is ready.

@kristaps-ancans
Copy link

Launching app with --disable-gpu works.

Seems that the same problem persisted on Ubuntu with HipChat, as it was unusable without --disable-gpu param.

@jarek-foksa
Copy link

jarek-foksa commented Oct 18, 2017

As a temporary workaround, perhaps Electron could check whether it is running on Windows build 10.0.16257.1 or later and automatically disable hardware acceleration? This appears to be a critical issue.

@MarshallOfSound
Copy link
Member

I'm running 17017 and not having this issue, not sure it's caused by the insider builds

@jarek-foksa
Copy link

jarek-foksa commented Oct 18, 2017

@Pokechu22, @kristaps-ancans Did you use a virtual machine to test the apps? Can you confirm this issue also happens when not using a virtual machine?

@kristaps-ancans
Copy link

@jarek-foksa not using virtual machine. Maybe it's related to 2 graphic cards? Have built in Intel one and NVIDIA GeForce.

@Pokechu22
Copy link
Author

Pokechu22 commented Oct 18, 2017 via email

@codebytere
Copy link
Member

We are no longer implementing bugfixes for versions of Electron <= 1.7.x, so i'm going to close this issue but if it is still persisting in more recent versions of Electron we can certainly reopen it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants