Skip to content

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

Closed

Description

  • 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

Activity

  1. isidorn commented on Oct 3, 2017

    @isidorn

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

  2. EagleEYErus commented on Oct 3, 2017

    @EagleEYErus
    Author

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

  3. isidorn commented on Oct 3, 2017

    @isidorn

    Alexander Saprykin (@EagleEYErus) without the sequence of steps there is not much we can do

  4. chasegiunta commented on Oct 4, 2017

    @chasegiunta

    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.

  5. chasegiunta commented on Oct 4, 2017

    @chasegiunta

    Alexander Saprykin (@EagleEYErus) are you using an external monitor by chance? Is it high dpi?

  6. bpasero commented on Oct 4, 2017

    @bpasero
    Contributor

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

  7. elijnzaad commented on Oct 4, 2017

    @elijnzaad

    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.

  8. bpasero commented on Oct 4, 2017

    @bpasero
    Contributor

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

  9. elijnzaad commented on Oct 4, 2017

    @elijnzaad

    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.

  10. bpasero commented on Oct 4, 2017

    @bpasero
    Contributor
  11. 73 remaining items

  12. s10mcow commented on Nov 2, 2017

    @s10mcow

    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? Benjamin Pasero (@bpasero)

  13. bpasero commented on Nov 2, 2017

    @bpasero
    Contributor

    @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.

  14. mehulkar commented on Nov 4, 2017

    @mehulkar

    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.

  15. stuartaccent commented on Nov 9, 2017

    @stuartaccent

    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 :)

  16. trumbitta commented on Nov 9, 2017

    @trumbitta

    Stuart George (@stuartaccent) how come NVIDIA provides official drivers via tonymacx86.com?

  17. stuartaccent commented on Nov 9, 2017

    @stuartaccent

    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

  18. bpasero commented on Nov 16, 2017

    @bpasero
    Contributor

    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.

  19. sledsworth commented on Nov 17, 2017

    @sledsworth

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

  20. s10mcow commented on Nov 17, 2017

    @s10mcow

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

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

  21. locked and limited conversation to collaborators on Dec 31, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

electronIssues and items related to Electroninfo-neededIssue requires more information from postermacosIssues with VS Code on MAC/OS XupstreamIssue identified as 'upstream' component related (exists outside of VS Code)

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions