-
Notifications
You must be signed in to change notification settings - Fork 27.9k
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
VSCode Insiders Blank Screen #23639
Comments
Did you try with the latest update? If you still see this, can you see something in the console or in the developer tools (Help > Toggle Developer Tools) |
Downloaded New version : 6b95480 Still seeing the same issue, |
Can you check the Console tab in the dev tools? |
Yes, I can see Console tab... please list me that steps, commands/log files that I can share with u to solve this issue. |
@charankumarpalla Please click the 'Console' tab in the 'Developer Tools' window and post what is shown there (or attach a screenshot). |
@chrmarti the workaround for me right now is:
Update: |
I do not know if it will be a solution ,,, What happens when renaming Note: |
@hrgui to be clear, you see this blank window only when clicking on the Code icon in the dock, but not when running from the command line? |
@bpasero correct. From the command line, it looks like this: |
@hrgui how about running the binary directly from the command line:
|
I am sorry for making you misunderstand.
I encountered similar problems in the past and had experience recovering by deleting directories. |
@bpasero that results in the blank screen / nothing in devtools console |
@hrgui how about Any output in the terminal? |
terminal shows:
This is how code --verbose looks like:
|
@hrgui how about downloading the entire app again to another location (e.g. downloads folder) and start it from there? |
So I downloaded, put it in home directory, ran (Also, do you know of a way to make the logs collapsable? i don't want to clutter this thread with logs)
|
@hrgui no worries about spamming this thread! ok so it seems to be unrelated from where you start it. I wonder if we can debug this better from within the application's blank screen: when you open dev tools in there and click on the sources tab, there is a way to let the debugger stop "pause on exceptions" (the blue thing in my screenshot) as well as "Pause on uncaught exceptions". Can you:
If it does not break, click on the other checkbox ("Pause on uncaught exceptions")
|
Stepping through some more:
So far I don't see any other errors beside those... I'll investigate some more when I have time. |
@hrgui thanks, this is weird. does it reproduce when you try our insiders channel? You can give our preview releases a try from: http://code.visualstudio.com/Download#insiders |
This is happening to me as well (blank screen). I just updated to I deleted the mainline app and tried redownloading with no success, and vs insiders (fresh download) shows the same symptoms. Insider build is at c905143 Nothing is being printed in developer tools console. Removed |
@aeschli This happened to me 3 times today (once in the office, twice at home). After quit, it started up fine. |
@joaomoreno how did you recover from it? |
@bpasero that's what I got in |
Mine is similar to @cbrevik , except, begin: getUnixShellEnvironment fires 4 times:
|
The fix for #21655 is the probable cause of this mess. |
@joaomoreno I'll double check to confirm.
|
@bpasero Just |
@hrgui Yep, reverting that also fixed it for me. |
What shells do you guys use? |
@joaomoreno I primarily use fishshell |
@joaomoreno I use zsh, but chsh to zsh doesn't work for me, so for me it's just plain old bash when vscode reads it correction: today i can finally chsh to zsh |
Ok thanks, this indicates to me that the process we fork is never finishing and never produces any output. Maybe it is waiting on |
Reverted the fix for #21655, will engage on better understanding the underlying issue. Thanks for all the help guys. We'll get this fix out asap. |
Adding verified label since we have at least 2 users confirming the fix solved the issue for them |
I was having this issue (#23639 (comment)) and updated my copy of VS Insiders this morning. It now works. 👍 (I too am using fish) |
@ograycode thanks for letting us know |
Steps to Reproduce:
The text was updated successfully, but these errors were encountered: