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 1.25 portable mode doesnt show GUI if started from network share #53857

Closed
jotrueck opened this issue Jul 9, 2018 · 6 comments · Fixed by #66128
Closed

VSCode 1.25 portable mode doesnt show GUI if started from network share #53857

jotrueck opened this issue Jul 9, 2018 · 6 comments · Fixed by #66128
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug help wanted Issues identified as good community contribution opportunities portable-mode VS Code portable mode issues verified Verification succeeded windows VS Code on Windows issues

Comments

@jotrueck
Copy link

jotrueck commented Jul 9, 2018

  • VSCode Version:1.25
  • OS Version:Windows Server 2012r2 / Win 10

Steps to Reproduce:

  1. Copy 1.25 to an Network share. create an .\data folder to make it an portable
  2. Start code.exe
  3. code.exe runs as background process in task manager. No Gui is shown
  4. Running code.exe on Fileserver from local Filesystem works as expected with gui in portable mode.

Does this issue occur when all extensions are disabled?: Yes

@jotrueck
Copy link
Author

jotrueck commented Jul 9, 2018

Just found out it happens only if started from UNC path. If you map a drive it works as expected.

@joaomoreno joaomoreno added bug Issue identified by VS Code Team member as probable bug portable-mode VS Code portable mode issues labels Jul 9, 2018
@joaomoreno joaomoreno added this to the July 2018 milestone Jul 9, 2018
@joaomoreno joaomoreno added the windows VS Code on Windows issues label Jul 9, 2018
@joaomoreno joaomoreno modified the milestones: July 2018, Backlog Jul 18, 2018
@joaomoreno joaomoreno added the help wanted Issues identified as good community contribution opportunities label Jul 18, 2018
@joaomoreno
Copy link
Member

/duplicate #58853

@vscodebot vscodebot bot added the *duplicate Issue identified as a duplicate of another issue(s) label Sep 19, 2018
@vscodebot
Copy link

vscodebot bot commented Sep 19, 2018

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for existing issues here. See also our issue reporting guidelines.

Happy Coding!

@vscodebot vscodebot bot closed this as completed Sep 19, 2018
@the-ress
Copy link
Contributor

@joaomoreno #58853 isn’t a duplicate of this issue

@joaomoreno
Copy link
Member

Thanks @the-ress, my bad.

@joaomoreno joaomoreno reopened this Sep 20, 2018
@joaomoreno joaomoreno removed the *duplicate Issue identified as a duplicate of another issue(s) label Sep 20, 2018
@joaomoreno
Copy link
Member

@jotrueck Can you go through this checklist, so we figure out what goes wrong?

Here is a checklist to find out more about the freeze/slow/crash

  • it reproduces with extensions disabled (code --disable-extensions from the command line - NOT the integrated terminal of Code)
    • if it does not reproduce with extensions disabled, you can stop testing and report this!
  • it was not happening in the previous stable release
  • it reproduces in insiders builds (get it from here)
  • there is no suspicious output when running from the command line (code --verbose)
  • there is no suspicious output in the window itself (Help | Toggle Developer Tools | Console)
  • it reproduces on Windows, Linux and Mac
  • it reproduces after deleting <appdata>/User/keybindings.json and <appdata>/User/settings.json (backup first! see below for paths)
  • it reproduces when opening empty (code -n from the command line)
  • it reproduces opening any folder
  • it reproduces opening any file
  • it reproduces when only having a single window open
  • it reproduces by just using Code without external tools running on the same folder
  • it reproduces from a workspace that is not under Git version control
  • it reproduces independently if a file is opened or not after startup
  • it reproduces when running with GPU disabled (code --disable-gpu)
  • it reproduces when being offline
  • it reproduces when disabling the file watching (set files.watcherExclude to "**/**": true)
  • it reproduces after uninstalling and reinstalling
  • it reproduces after deleting the application data directory (backup first! see below for paths)
  • I have not played around with permissions or ran Code as administrator
  • I am seeing a single CPU process spin high (please share the full command line arguments)
  • I am seeing Code consuming lots of memory in a short time

Application Data Directory for VS Code:

  • Windows: C:\Users\<user>\AppData\Roaming\Code
  • Mac: /Users/<user>/Library/Application Support/Code
  • Linux: /home/<user>/.config/Code

Application Data Directory for VS Code Insiders:

  • Windows: C:\Users\<user>\AppData\Roaming\Code - Insiders
  • Mac: /Users/<user>/Library/Application Support/Code - Insiders
  • Linux: /home/<user>/.config/Code - Insiders

the-ress added a commit to the-ress/vscode that referenced this issue Jan 7, 2019
@bpasero bpasero modified the milestones: Backlog, December/January 2019 Jan 7, 2019
bpasero pushed a commit that referenced this issue Jan 7, 2019
@roblourens roblourens added the verified Verification succeeded label Feb 1, 2019
@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug help wanted Issues identified as good community contribution opportunities portable-mode VS Code portable mode issues verified Verification succeeded windows VS Code on Windows issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants