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

macOS High Sierra: parts of the UI not rendering #35527

Closed
EagleEYErus opened this Issue Oct 3, 2017 · 81 comments

Comments

Projects
None yet
@EagleEYErus

EagleEYErus commented Oct 3, 2017

  • VSCode Version: 1.16.1
  • OS Version: macOS High Sierra 10.13

Steps to Reproduce:

Interface crashes when I open a file in the project folder tree.

Reproduces without extensions: Not Tested

@vscodebot vscodebot bot added the workbench label Oct 3, 2017

@isidorn

This comment has been minimized.

Show comment
Hide comment
@isidorn

isidorn Oct 3, 2017

Contributor

Can you reproduce this with vscode insiders?
https://code.visualstudio.com/Insiders/

Contributor

isidorn commented Oct 3, 2017

Can you reproduce this with vscode insiders?
https://code.visualstudio.com/Insiders/

@bpasero bpasero added this to the Backlog milestone Oct 3, 2017

@EagleEYErus

This comment has been minimized.

Show comment
Hide comment
@EagleEYErus

EagleEYErus Oct 3, 2017

@isidorn I will try, but I have not yet understood the sequence of steps to cause the crash. This happens randomly.

EagleEYErus commented Oct 3, 2017

@isidorn I will try, but I have not yet understood the sequence of steps to cause the crash. This happens randomly.

@isidorn

This comment has been minimized.

Show comment
Hide comment
@isidorn

isidorn Oct 3, 2017

Contributor

@EagleEYErus without the sequence of steps there is not much we can do

Contributor

isidorn commented Oct 3, 2017

@EagleEYErus without the sequence of steps there is not much we can do

@chasegiunta

This comment has been minimized.

Show comment
Hide comment
@chasegiunta

chasegiunta Oct 4, 2017

I’ve also recently had this begin happening after update to High Sierra, though it’s not specific to opening a file in tree. Completely random. It also appears to happen on other electron apps (Slack) though I haven’t been able to track down an electron issue for it anywhere yet.

chasegiunta commented Oct 4, 2017

I’ve also recently had this begin happening after update to High Sierra, though it’s not specific to opening a file in tree. Completely random. It also appears to happen on other electron apps (Slack) though I haven’t been able to track down an electron issue for it anywhere yet.

@chasegiunta

This comment has been minimized.

Show comment
Hide comment
@chasegiunta

chasegiunta Oct 4, 2017

@EagleEYErus are you using an external monitor by chance? Is it high dpi?

chasegiunta commented Oct 4, 2017

@EagleEYErus are you using an external monitor by chance? Is it high dpi?

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Oct 4, 2017

Member

@chasegiunta does it make a difference if you run "code --disable-gpu" from the command line?

Member

bpasero commented Oct 4, 2017

@chasegiunta does it make a difference if you run "code --disable-gpu" from the command line?

@elijnzaad

This comment has been minimized.

Show comment
Hide comment
@elijnzaad

elijnzaad Oct 4, 2017

I've experienced similar problems since upgrading to High Sierra. After a while the screen goes to a screen like EagleEYErus's. The after a minute or so it gradually comes back to life. I am using a MacBook Pro with a 4K external monitor, but I've experienced the same problems while not using the monitor.

Running "open Visual\ Studio\ Code.app --args --disable-gpu" from the terminal seems to have fixed the problem. It is running trouble-free for about an hour now.

elijnzaad commented Oct 4, 2017

I've experienced similar problems since upgrading to High Sierra. After a while the screen goes to a screen like EagleEYErus's. The after a minute or so it gradually comes back to life. I am using a MacBook Pro with a 4K external monitor, but I've experienced the same problems while not using the monitor.

Running "open Visual\ Studio\ Code.app --args --disable-gpu" from the terminal seems to have fixed the problem. It is running trouble-free for about an hour now.

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Oct 4, 2017

Member

@EagleEYErus @elijnzaad does it run any better with our insiders build (NOT using --disable-gpu): http://code.visualstudio.com/Download#insiders

Member

bpasero commented Oct 4, 2017

@EagleEYErus @elijnzaad does it run any better with our insiders build (NOT using --disable-gpu): http://code.visualstudio.com/Download#insiders

@elijnzaad

This comment has been minimized.

Show comment
Hide comment
@elijnzaad

elijnzaad Oct 4, 2017

No, it doesn't.
Although I'm not sure I actually got the insiders build. I did follow your link, but the 'about' still shows 1.16.1.

elijnzaad commented Oct 4, 2017

No, it doesn't.
Although I'm not sure I actually got the insiders build. I did follow your link, but the 'about' still shows 1.16.1.

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero
Member

bpasero commented Oct 4, 2017

@elijnzaad

This comment has been minimized.

Show comment
Hide comment
@elijnzaad

elijnzaad Oct 4, 2017

I'm sorry, but the insiders build does have the same problem as the production build. It didn't take me more than 2 minutes. The screenshot shows the first thing I did, which is adjusting the user settings.
screen shot 2017-10-04 at 11 38 56

elijnzaad commented Oct 4, 2017

I'm sorry, but the insiders build does have the same problem as the production build. It didn't take me more than 2 minutes. The screenshot shows the first thing I did, which is adjusting the user settings.
screen shot 2017-10-04 at 11 38 56

@EagleEYErus

This comment has been minimized.

Show comment
Hide comment
@EagleEYErus

EagleEYErus Oct 4, 2017

@chasegiunta I did not use external monitors at the time the error was received. The first time a bug appeared on the MacOS High Sierra on the MacBook Air 13' 2013. For one development session, UI crashed several times. Then I ran into this problem yesterday on my iMac 27' late 2013. Then I tried to cause the error intentionally, but I did not find the sequence of steps, although it arose again when I changed the application window, but when I tried to repeat these actions nothing happened. I do not remember exactly, but the discord also seemed to give out this crash.

EagleEYErus commented Oct 4, 2017

@chasegiunta I did not use external monitors at the time the error was received. The first time a bug appeared on the MacOS High Sierra on the MacBook Air 13' 2013. For one development session, UI crashed several times. Then I ran into this problem yesterday on my iMac 27' late 2013. Then I tried to cause the error intentionally, but I did not find the sequence of steps, although it arose again when I changed the application window, but when I tried to repeat these actions nothing happened. I do not remember exactly, but the discord also seemed to give out this crash.

@EagleEYErus

This comment has been minimized.

Show comment
Hide comment
@EagleEYErus

EagleEYErus Oct 4, 2017

@elijnzaad UI after the crash was restored only once otherwise I had to restart the application

EagleEYErus commented Oct 4, 2017

@elijnzaad UI after the crash was restored only once otherwise I had to restart the application

@EagleEYErus

This comment has been minimized.

Show comment
Hide comment
@EagleEYErus

EagleEYErus Oct 4, 2017

@elijnzaad Don't you have extensions for the insider version?

EagleEYErus commented Oct 4, 2017

@elijnzaad Don't you have extensions for the insider version?

@bpasero bpasero changed the title from UI Crash to macOS High Sierra: UI not rendering Oct 4, 2017

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Oct 4, 2017

Member

@EagleEYErus @elijnzaad does this only reproduce on external monitor or also on the macbook pro screen? for external monitor, are they 4k/5k monitors?

Member

bpasero commented Oct 4, 2017

@EagleEYErus @elijnzaad does this only reproduce on external monitor or also on the macbook pro screen? for external monitor, are they 4k/5k monitors?

@elijnzaad

This comment has been minimized.

Show comment
Hide comment
@elijnzaad

elijnzaad Oct 4, 2017

@EagleEYErus I actually hadn't done anything in the insider build. I downloaded it, started it and selected Preferences -> User settings from the menu. That's all, no extensions.

elijnzaad commented Oct 4, 2017

@EagleEYErus I actually hadn't done anything in the insider build. I downloaded it, started it and selected Preferences -> User settings from the menu. That's all, no extensions.

@EagleEYErus

This comment has been minimized.

Show comment
Hide comment
@EagleEYErus

EagleEYErus Oct 4, 2017

@bpasero I did not use external monitors during the crash, and, as I wrote above, the maximum resolution of all the devices I use is 2560x1440

The first time a bug appeared on the MacOS High Sierra on the MacBook Air 13' 2013. For one development session, UI crashed several times. Then I ran into this problem yesterday on my iMac 27' late 2013.

EagleEYErus commented Oct 4, 2017

@bpasero I did not use external monitors during the crash, and, as I wrote above, the maximum resolution of all the devices I use is 2560x1440

The first time a bug appeared on the MacOS High Sierra on the MacBook Air 13' 2013. For one development session, UI crashed several times. Then I ran into this problem yesterday on my iMac 27' late 2013.

@elijnzaad

This comment has been minimized.

Show comment
Hide comment
@elijnzaad

elijnzaad Oct 4, 2017

@bpasero I did use a Philips BDM4037U 4K external monitor. I'm currently running VSCode Insider without the external monitor on a MacBook Pro (Retina, Mid 2012), Graphics NVIDIA GeForce GT 650M 1 GB
Intel HD Graphics 4000 1536 MB. So far no problems yet.

elijnzaad commented Oct 4, 2017

@bpasero I did use a Philips BDM4037U 4K external monitor. I'm currently running VSCode Insider without the external monitor on a MacBook Pro (Retina, Mid 2012), Graphics NVIDIA GeForce GT 650M 1 GB
Intel HD Graphics 4000 1536 MB. So far no problems yet.

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Oct 4, 2017

Member

@EagleEYErus on what device are you seeing this currently?

@elijnzaad and this is without using --disable-gpu right?

Member

bpasero commented Oct 4, 2017

@EagleEYErus on what device are you seeing this currently?

@elijnzaad and this is without using --disable-gpu right?

@bpasero bpasero modified the milestones: Backlog, October 2017 Oct 4, 2017

@bpasero bpasero added the important label Oct 4, 2017

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Oct 25, 2017

Member

If anyone seeing this issue could report back if it still reproduces with this insider build: https://az764295.vo.msecnd.net/insider/7dec12f226bc98992bc8413340ea28281f6e94a0/VSCode-darwin-insider-unsigned.zip

Thanks!

Member

bpasero commented Oct 25, 2017

If anyone seeing this issue could report back if it still reproduces with this insider build: https://az764295.vo.msecnd.net/insider/7dec12f226bc98992bc8413340ea28281f6e94a0/VSCode-darwin-insider-unsigned.zip

Thanks!

@mrazahasan

This comment has been minimized.

Show comment
Hide comment
@mrazahasan

mrazahasan Oct 25, 2017

@bpasero nupz still UI not rendering properly. Its electron problem i guess. :(
screenshot at oct 25 21-48-28
screenshot at oct 25 21-51-21

mrazahasan commented Oct 25, 2017

@bpasero nupz still UI not rendering properly. Its electron problem i guess. :(
screenshot at oct 25 21-48-28
screenshot at oct 25 21-51-21

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Oct 25, 2017

Member

@mrazahasan I think you might be seeing something else, so far I thought this issue would only manifest on macOS high sierra.

Member

bpasero commented Oct 25, 2017

@mrazahasan I think you might be seeing something else, so far I thought this issue would only manifest on macOS high sierra.

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Oct 26, 2017

Member

@EagleEYErus @chasegiunta ping, do you still see it in todays insider update?

Member

bpasero commented Oct 26, 2017

@EagleEYErus @chasegiunta ping, do you still see it in todays insider update?

@brosner

This comment has been minimized.

Show comment
Hide comment
@brosner

brosner Oct 26, 2017

@bpasero I have been following this issue and have been experiencing it myself. I can confirm today's insider update is showing very positive signs of a fix. I have not yet seen the issue yet. I will continue to use it and see if it crops up as it is mostly random. One case that caused the issue for me before updating was with vigorous window resizing and I don't see it after updating.

brosner commented Oct 26, 2017

@bpasero I have been following this issue and have been experiencing it myself. I can confirm today's insider update is showing very positive signs of a fix. I have not yet seen the issue yet. I will continue to use it and see if it crops up as it is mostly random. One case that caused the issue for me before updating was with vigorous window resizing and I don't see it after updating.

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Oct 26, 2017

Member

@brosner awesome, thanks

Member

bpasero commented Oct 26, 2017

@brosner awesome, thanks

@chasegiunta

This comment has been minimized.

Show comment
Hide comment
@chasegiunta

chasegiunta Oct 26, 2017

@bpasero Would love to test this out today if there's an easy way to reliably bring all my extensions & settings into Insiders. Can I ask what potential fixes were made? Checking for GPU and/or device type and conditionally disabled GPU?

chasegiunta commented Oct 26, 2017

@bpasero Would love to test this out today if there's an easy way to reliably bring all my extensions & settings into Insiders. Can I ask what potential fixes were made? Checking for GPU and/or device type and conditionally disabled GPU?

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Oct 26, 2017

Member

@chasegiunta the fix disables certain GPU features when a NVIDIA GPU is detected.

For syncing, maybe try https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync

Member

bpasero commented Oct 26, 2017

@chasegiunta the fix disables certain GPU features when a NVIDIA GPU is detected.

For syncing, maybe try https://marketplace.visualstudio.com/items?itemName=Shan.code-settings-sync

@stenmuchow

This comment has been minimized.

Show comment
Hide comment
@stenmuchow

stenmuchow Oct 27, 2017

Every time I update OSX i get such crap... Im gonna try the insider update and see what happens. Remember when OSX made good softwear? Nah - me neither :(

stenmuchow commented Oct 27, 2017

Every time I update OSX i get such crap... Im gonna try the insider update and see what happens. Remember when OSX made good softwear? Nah - me neither :(

@stenmuchow

This comment has been minimized.

Show comment
Hide comment
@stenmuchow

stenmuchow Oct 27, 2017

@bpasero the insider install via the link you shared seems stable - for now.
screen shot 2017-10-27 at 12 33 26 pm

stenmuchow commented Oct 27, 2017

@bpasero the insider install via the link you shared seems stable - for now.
screen shot 2017-10-27 at 12 33 26 pm

@stenmuchow

This comment has been minimized.

Show comment
Hide comment
@stenmuchow

stenmuchow Nov 2, 2017

After using insiders for the last 5 days i confirm no more strange problems. Will this be moved to the regular vscode or do i continue to use insiders? @bpasero

stenmuchow commented Nov 2, 2017

After using insiders for the last 5 days i confirm no more strange problems. Will this be moved to the regular vscode or do i continue to use insiders? @bpasero

@bpasero bpasero removed the important label Nov 2, 2017

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Nov 2, 2017

Member

@stenmuchow thanks for the confirmation. Yes, the "fix" will go into stable. It is not a real fix of the underlying problem, rather we disable certain GPU features on certain hardware. So I would still like to keep this open and see if a real fix lands. The real fix might actually require Apple to fix something in High Sierra, so it might not even be possible to fix it in Electron.

Member

bpasero commented Nov 2, 2017

@stenmuchow thanks for the confirmation. Yes, the "fix" will go into stable. It is not a real fix of the underlying problem, rather we disable certain GPU features on certain hardware. So I would still like to keep this open and see if a real fix lands. The real fix might actually require Apple to fix something in High Sierra, so it might not even be possible to fix it in Electron.

@mehulkar

This comment has been minimized.

Show comment
Hide comment
@mehulkar

mehulkar Nov 4, 2017

Another piece of info that I didn't see in this thread on quick glance... after the glitches happened, I quit VSCode and then can't reopen it. It crashes immediately on launch. It's in that state right now. This has happened once before and a reboot fixed the issue. Let me know if I can get you any more info before I reboot! (I tried launching through CLI with some of the flags mentioned in this post, but it still crashes on launch immediately). I'll wait till tomorrow to reboot my machine and use a diferent editor till then.

mehulkar commented Nov 4, 2017

Another piece of info that I didn't see in this thread on quick glance... after the glitches happened, I quit VSCode and then can't reopen it. It crashes immediately on launch. It's in that state right now. This has happened once before and a reboot fixed the issue. Let me know if I can get you any more info before I reboot! (I tried launching through CLI with some of the flags mentioned in this post, but it still crashes on launch immediately). I'll wait till tomorrow to reboot my machine and use a diferent editor till then.

@stuartaccent

This comment has been minimized.

Show comment
Hide comment
@stuartaccent

stuartaccent Nov 9, 2017

just for info and sorry if u already know all this.

Have OSX 10.13.1 with NVIDIA GeForce GTX 660M 512 MB and just downloaded nvidias own drivers from https://www.tonymacx86.com/nvidia-drivers. So far all glitches have gone for any app using electron. Im a happy man again :)

stuartaccent commented Nov 9, 2017

just for info and sorry if u already know all this.

Have OSX 10.13.1 with NVIDIA GeForce GTX 660M 512 MB and just downloaded nvidias own drivers from https://www.tonymacx86.com/nvidia-drivers. So far all glitches have gone for any app using electron. Im a happy man again :)

@trumbitta

This comment has been minimized.

Show comment
Hide comment
@trumbitta

trumbitta Nov 9, 2017

@stuartaccent how come NVIDIA provides official drivers via tonymacx86.com?

trumbitta commented Nov 9, 2017

@stuartaccent how come NVIDIA provides official drivers via tonymacx86.com?

@stuartaccent

This comment has been minimized.

Show comment
Hide comment
@stuartaccent

stuartaccent Nov 9, 2017

thats just a page with links ie: macOS 10.13.1 High Sierra = https://images.nvidia.com/mac/pkg/378/WebDriver-378.10.10.10.20.107.pkg

stuartaccent commented Nov 9, 2017

thats just a page with links ie: macOS 10.13.1 High Sierra = https://images.nvidia.com/mac/pkg/378/WebDriver-378.10.10.10.20.107.pkg

@bpasero bpasero removed the workbench label Nov 12, 2017

@bpasero

This comment has been minimized.

Show comment
Hide comment
@bpasero

bpasero Nov 16, 2017

Member

Closing, since our workaround is in and Chrome has fixed this meanwhile, we just need to pick it up in one of our future Electron updates.

Member

bpasero commented Nov 16, 2017

Closing, since our workaround is in and Chrome has fixed this meanwhile, we just need to pick it up in one of our future Electron updates.

@bpasero bpasero closed this Nov 16, 2017

@sledsworth

This comment has been minimized.

Show comment
Hide comment
@sledsworth

sledsworth Nov 17, 2017

Did this ever actually get fixed or is the ‘fix’ still disabling hardware on Macs with Nvidia cards?

sledsworth commented Nov 17, 2017

Did this ever actually get fixed or is the ‘fix’ still disabling hardware on Macs with Nvidia cards?

@stenmuchow

This comment has been minimized.

Show comment
Hide comment
@stenmuchow

stenmuchow Nov 17, 2017

Seems updating NVIDIA drivers has given my machine a more stable feel... Using link from @stuartaccent

FYI - i have a late 2014 15" MBP with 2GB NVIDIA 750 geforce

stenmuchow commented Nov 17, 2017

Seems updating NVIDIA drivers has given my machine a more stable feel... Using link from @stuartaccent

FYI - i have a late 2014 15" MBP with 2GB NVIDIA 750 geforce

@vscodebot vscodebot bot locked and limited conversation to collaborators Dec 31, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.