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

VSCode Insiders Blank Screen #23639

Closed
charankumarpalla opened this issue Mar 30, 2017 · 71 comments
Closed

VSCode Insiders Blank Screen #23639

charankumarpalla opened this issue Mar 30, 2017 · 71 comments
Assignees
Labels
important Issue identified as high-priority verified Verification succeeded

Comments

@charankumarpalla
Copy link

  • VSCode Version: Version 1.11.0-insider (1.11.0-insider) d98a518
  • OS Version: mac Sierra 10.12.2

Steps to Reproduce:

  1. As Of This issues : vscode/issues/2806, Downloaded VS Code From https://code.visualstudio.com/insiders
  2. When I Open VSCode, it comes just Blank , None of the option works

screen shot 2017-03-30 at 10 29 53 am

@aeschli
Copy link
Contributor

aeschli commented Mar 30, 2017

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)

@aeschli aeschli added the info-needed Issue requires more information from poster label Mar 30, 2017
@charankumarpalla
Copy link
Author

Downloaded New version : 6b95480

Still seeing the same issue,

I'm able to open developer tools
screen shot 2017-03-30 at 1 33 34 pm

@aeschli
Copy link
Contributor

aeschli commented Mar 30, 2017

Can you check the Console tab in the dev tools?

@charankumarpalla
Copy link
Author

charankumarpalla commented Apr 3, 2017

Yes, I can see Console tab...

please list me that steps, commands/log files that I can share with u to solve this issue.

@chrmarti chrmarti self-assigned this Apr 4, 2017
@chrmarti
Copy link
Contributor

chrmarti commented Apr 4, 2017

@charankumarpalla Please click the 'Console' tab in the 'Developer Tools' window and post what is shown there (or attach a screenshot).

@hrgui
Copy link

hrgui commented Apr 5, 2017

@chrmarti the workaround for me right now is:
OS : Mac OS X Sierra 10.2.4
Code 1.11 Stable

code --verbose

Update:
It looks like if I load Code from terminal it works, but if i don't load it from terminal (e.g. finder) it doesnt work

@chrmarti chrmarti assigned bpasero and unassigned chrmarti Apr 5, 2017
@satokaz
Copy link
Contributor

satokaz commented Apr 6, 2017

I do not know if it will be a solution ,,,

What happens when renaming $HOME/Library/Application Support/Code - Insiders directory from Terminal and Invoke code from finder?

Note: $HOME/Library/Application Support/Code - Insiders contains some important files such as settings.json. Do not erase it.

@bpasero bpasero added this to the Backlog milestone Apr 6, 2017
@bpasero
Copy link
Member

bpasero commented Apr 6, 2017

@hrgui @satokaz when this happens can you see if there is some output in the console printed?

image

@hrgui
Copy link

hrgui commented Apr 6, 2017

Unfortunately, there isn't anything in the console:

screen shot 2017-04-05 at 10 13 55 pm

What I also do know in this mode, in 1.10.2, I had this problem with debugger that says the following:

"Cannot find node in path"

Would that be related by any chance?

@bpasero
Copy link
Member

bpasero commented Apr 6, 2017

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

@hrgui
Copy link

hrgui commented Apr 6, 2017

@bpasero correct. From the command line, it looks like this:
screen shot 2017-04-05 at 10 21 11 pm

@bpasero
Copy link
Member

bpasero commented Apr 6, 2017

@hrgui how about running the binary directly from the command line:

/Applications/Visual Studio Code.app/Contents/MacOS> ./Electron

@satokaz
Copy link
Contributor

satokaz commented Apr 6, 2017

@bpasero

I am sorry for making you misunderstand.
In my environment code v1.11 and code-insiders 1.11.0 2017-04-04T21:06:37.100Z works fine.

  • VSCode Version: Code 1.11.0 (9122ec4, 2017-04-05T20:52:01.201Z)
  • OS Version: Darwin x64 16.5.0 (macOS sierra 10.12.4)

I encountered similar problems in the past and had experience recovering by deleting directories.

@hrgui
Copy link

hrgui commented Apr 6, 2017

@bpasero that results in the blank screen / nothing in devtools console

@bpasero
Copy link
Member

bpasero commented Apr 6, 2017

@hrgui how about /Applications/Visual Studio Code.app/Contents/MacOS> ./Electron --verbose

Any output in the terminal?

@hrgui
Copy link

hrgui commented Apr 6, 2017

terminal shows:

/Applications/Visual Studio Code.app/Contents/MacOS> ./Electron --verbose
➜  MacOS ./Electron --verbose
[main 10:40:31 PM] Starting VS Code in verbose mode
[main 10:40:31 PM] from: /Applications/Visual Studio Code.app/Contents/Resources/app
[main 10:40:31 PM] args: { _: [],
  help: false,
  h: false,
  version: false,
  v: false,
  wait: false,
  w: false,
  diff: false,
  d: false,
  goto: false,
  g: false,
  'new-window': false,
  n: false,
  'unity-launch': false,
  'reuse-window': false,
  r: false,
  performance: false,
  p: false,
  'prof-startup': false,
  verbose: true,
  logExtensionHostCommunication: false,
  'disable-extensions': false,
  disableExtensions: false,
  'list-extensions': false,
  'show-versions': false,
  nolazy: false }

This is how code --verbose looks like:

➜  MacOS code --verbose
[main 10:42:22 PM] Starting VS Code in verbose mode
[main 10:42:22 PM] from: /Applications/Visual Studio Code.app/Contents/Resources/app
[main 10:42:22 PM] args: { _: [],
  help: false,
  h: false,
  version: false,
  v: false,
  wait: false,
  w: false,
  diff: false,
  d: false,
  goto: false,
  g: false,
  'new-window': false,
  n: false,
  'unity-launch': false,
  'reuse-window': false,
  r: false,
  performance: false,
  p: false,
  'prof-startup': false,
  verbose: true,
  logExtensionHostCommunication: false,
  'disable-extensions': false,
  disableExtensions: false,
  'list-extensions': false,
  'show-versions': false,
  nolazy: false }
[main 10:42:23 PM] IPC#vscode-machineId
[89614:0405/224224:INFO:CONSOLE(28)] "Overwriting extension <<.ejs>> to now point to mime <<text/x-ejs>>", source: file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[89614:0405/224224:INFO:CONSOLE(28)] "Overwriting extension <<.jsx>> to now point to mime <<text/x-jsx>>", source: file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[main 10:42:25 PM] IPC#vscode-workbenchLoaded
[89614:0405/224226:INFO:CONSOLE(28)] "%c[IPC Library: Watcher]", source: file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)
[89614:0405/224226:INFO:CONSOLE(28)] "%c[IPC Library: Watcher]", source: file:////Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/electron-browser/workbench.main.js (28)

@bpasero
Copy link
Member

bpasero commented Apr 6, 2017

@hrgui how about downloading the entire app again to another location (e.g. downloads folder) and start it from there?

Link: https://az764295.vo.msecnd.net/stable/9122ec4b1068bd391e41974f46a4b54c1b9c90f9/VSCode-darwin-stable.zip

@hrgui
Copy link

hrgui commented Apr 6, 2017

So I downloaded, put it in home directory, ran /Users/harman.goei/Visual Studio Code.app/Contents/MacOS/Electron --verbose, and it seems to do the same thing.

(Also, do you know of a way to make the logs collapsable? i don't want to clutter this thread with logs)

➜  MacOS pwd
/Users/harman.goei/Visual Studio Code.app/Contents/MacOS
➜  MacOS ./Electron --verbose
[main 10:46:51 PM] Sending env to running instance...
[main 10:46:51 PM] Sent env to running instance. Terminating...
➜  MacOS ./Electron --verbose
[main 10:46:58 PM] Starting VS Code in verbose mode
[main 10:46:58 PM] from: /Users/harman.goei/Visual Studio Code.app/Contents/Resources/app
[main 10:46:58 PM] args: { _: [],
  help: false,
  h: false,
  version: false,
  v: false,
  wait: false,
  w: false,
  diff: false,
  d: false,
  goto: false,
  g: false,
  'new-window': false,
  n: false,
  'unity-launch': false,
  'reuse-window': false,
  r: false,
  performance: false,
  p: false,
  'prof-startup': false,
  verbose: true,
  logExtensionHostCommunication: false,
  'disable-extensions': false,
  disableExtensions: false,
  'list-extensions': false,
  'show-versions': false,
  nolazy: false }

@bpasero
Copy link
Member

bpasero commented Apr 6, 2017

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

image

Can you:

  • first just have the blue thing checked
  • press Cmd+R from when devtools has focus anywhere
  • this should reload the window and it may break in the debugger if there is an error
  • if so, please let me know

If it does not break, click on the other checkbox ("Pause on uncaught exceptions")

  • follow the same steps
  • you will hit some errors right away that are unrelated, mainly return process.binding(atom_${process.type}_${name}) and return process.binding('icu'); but I wonder if there is another error hit after that?

@hrgui
Copy link

hrgui commented Apr 6, 2017

screen shot 2017-04-05 at 10 56 24 pm

Error: No such module: atom_renderer_v8_util
    at Error (native)
    at process.atomBinding (/Applications/Visual Studio Code.app/Contents/Resources/electron.asar/common/init.js:5:20)
    at Object.<anonymous> (/Applications/Visual Studio Code.app/Contents/Resources/electron.asar/renderer/init.js:23:22)
    at Module._compile (module.js:556:32)
    at Object.Module._extensions..js (module.js:565:10)
    at Module.load (module.js:473:32)
    at tryModuleLoad (module.js:432:12)
    at Function.Module._load (module.js:424:3)
    at Module.runMain (module.js:590:10)
    at run (bootstrap_node.js:402:7)

Stepping through some more:

Error: No such module: icu
    at Error (native)
    at importPunycode (url.js:5:20)
    at url.js:11:21
    at NativeModule.compile (bootstrap_node.js:505:7)
    at Function.NativeModule.require (bootstrap_node.js:446:18)
    at Function.Module._load (module.js:412:25)
    at Module.require (module.js:483:17)
    at require (internal/module.js:20:19)
    at s (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/loader.js:4:25882)
    at t.load (file:///Applications/Visual%20Studio%20Code.app/Contents/Resources/app/out/vs/loader.js:4:10583)

So far I don't see any other errors beside those... I'll investigate some more when I have time.

@bpasero
Copy link
Member

bpasero commented Apr 6, 2017

@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

@ograycode
Copy link

ograycode commented Apr 6, 2017

This is happening to me as well (blank screen). I just updated to 1.11.0 (9122ec4) after being prompted, using osx version 10.11.4.

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 Code from ~/Library/Application Support and still failed to start properly.

@joaomoreno
Copy link
Member

joaomoreno commented Apr 6, 2017

@aeschli This happened to me 3 times today (once in the office, twice at home).

After quit, it started up fine.

@bpasero
Copy link
Member

bpasero commented Apr 6, 2017

@joaomoreno how did you recover from it?

@cbrevik
Copy link

cbrevik commented Apr 7, 2017


begin: getUnixShellEnvironment()
1
2
3
4
5
6
7
8
9

@bpasero that's what I got in out.log

@hrgui
Copy link

hrgui commented Apr 7, 2017

Mine is similar to @cbrevik , except, begin: getUnixShellEnvironment fires 4 times:

begin: getUnixShellEnvironment()
begin: getUnixShellEnvironment()
begin: getUnixShellEnvironment()
begin: getUnixShellEnvironment()
1
2
3
4
5
6
7
8
9%

@joaomoreno
Copy link
Member

joaomoreno commented Apr 7, 2017

The fix for #21655 is the probable cause of this mess.

@bpasero
Copy link
Member

bpasero commented Apr 7, 2017

@hrgui @cbrevik almost there, can you do the exact same steps again, I have updated the getUnixShellEnvironment() code a little bit and attach the output here?

@hrgui
Copy link

hrgui commented Apr 7, 2017

@joaomoreno
I reverted the fix on main.js to reflect 78bc68a and it seems like that is the culprit.

I'll double check to confirm.

@bpasero

                fs.appendFileSync(logpath, "\n6");
                var child = cp.spawn(process.env.SHELL, ['-ilc', command], {
                    detached: true,
                    stdio: ['ignore', 'pipe', process.stderr],  // i changed this line from 'pipe' to 'ignore'
                    env: env
                });
                fs.appendFileSync(logpath, "\n7");

@cbrevik
Copy link

cbrevik commented Apr 7, 2017

@bpasero Just begin: getUnixShellEnvironment() and before: process.lazyEnv again now

@cbrevik
Copy link

cbrevik commented Apr 7, 2017

@hrgui Yep, reverting that also fixed it for me.

@joaomoreno
Copy link
Member

What shells do you guys use?

@cbrevik
Copy link

cbrevik commented Apr 7, 2017

@joaomoreno I primarily use fishshell

@hrgui
Copy link

hrgui commented Apr 7, 2017

@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

@bpasero
Copy link
Member

bpasero commented Apr 7, 2017

@chrmarti @hrgui you are not getting any output anymore in out.log after my latest getUnixShellEnvironment() ?

@cbrevik
Copy link

cbrevik commented Apr 7, 2017

@bpasero only begin: getUnixShellEnvironment(). After reverting like @hrgui described I'm getting a whole lot more though.

(You removed the counting log I saw though?)

@bpasero
Copy link
Member

bpasero commented Apr 7, 2017

Ok thanks, this indicates to me that the process we fork is never finishing and never produces any output. Maybe it is waiting on stdin for something.

@joaomoreno
Copy link
Member

joaomoreno commented Apr 7, 2017

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.

@isidorn
Copy link
Contributor

isidorn commented Apr 12, 2017

Adding verified label since we have at least 2 users confirming the fix solved the issue for them

@isidorn isidorn added the verified Verification succeeded label Apr 12, 2017
@ograycode
Copy link

ograycode commented Apr 12, 2017

I was having this issue (#23639 (comment)) and updated my copy of VS Insiders this morning. It now works. 👍

(I too am using fish)

@isidorn
Copy link
Contributor

isidorn commented Apr 12, 2017

@ograycode thanks for letting us know

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
important Issue identified as high-priority verified Verification succeeded
Projects
None yet
Development

No branches or pull requests