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

Extension host terminates when editing code offline #372

Closed
Glober777 opened this issue Dec 13, 2016 · 8 comments
Closed

Extension host terminates when editing code offline #372

Glober777 opened this issue Dec 13, 2016 · 8 comments
Labels
Bug: VS Code Bugs in VS Code itself. Issue-Bug A bug to squash.

Comments

@Glober777
Copy link

Please fill in these details so that we can help you!

System Details

  • Operating system name and version: Windows 10 Enterprise
  • VS Code version: vscode-powershell
  • PowerShell extension version: 0.7.2
  • Output from $PSVersionTable:
    PS > $PSVersionTable

Name Value


PSVersion 5.1.14393.479
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14393.479
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1

Issue Description

Today, I've received a few 'Extension host terminated' errors when I was editing the code while being disconnected from the network (LAN not connected and WiFi adapter disabled). When I hit this it reminded me about issue #353 (if wonder if these are related), although in my case I wasn't trying to run a debugger but just was editing some PS code.

Attached Logs

Logs sent over email.

@daviwil daviwil added this to the 0.9.0 milestone Dec 14, 2016
@daviwil daviwil added Issue-Bug A bug to squash. Bug: VS Code Bugs in VS Code itself. labels Dec 14, 2016
@daviwil daviwil modified the milestones: 0.9.0, 0.8.1 Dec 16, 2016
@daviwil daviwil modified the milestones: 0.9.0, 0.9.1 Jan 18, 2017
@daviwil daviwil modified the milestones: 0.9.1, 0.10.1, 0.10.2 Mar 14, 2017
@daviwil
Copy link
Contributor

daviwil commented Mar 24, 2017

Hey @Glober777, do you still see this issue in more recent builds of VS Code and the PS extension?

@daviwil daviwil modified the milestones: Next Patch Update, 0.10.2 Mar 24, 2017
@Glober777
Copy link
Author

Hey @daviwil, I haven't faced with this issue since I submitted a bug for it, however I haven't been using VSCode offline either.

@daviwil
Copy link
Contributor

daviwil commented Mar 26, 2017

No problem! I'll try to reproduce this sometime and see if I hit the same issue before I close this bug.

@BernieWhite
Copy link

BernieWhite commented Apr 5, 2017

There is still an issue there @daviwil @Glober777. I don't receive a error message. However the extension reports "Starting PowerShell..." and never completes.

VSCode: 1.10.2
ms-vscode.PowerShell: 0.12.1

PSVersion: 5.1.14393.953
PSEdition: Desktop
PSCompatibleVersions: {1.0, 2.0, 3.0, 4.0...}
BuildVersion: 10.0.14393.953
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1

vscode-powershell.log

[8:30:47] Language server starting...
powershell.exe started --
powershell.exe started --
powershell.exe started --
powershell.exe started --
[8:30:51] Language server started.
Connecting to language service on port 14818...

editorservices.log

6/04/2017 8:30:49 AM [NORMAL] - Method "StartLogging" at line 124 of >C:\projects\powershelleditorservices\src\PowerShellEditorServices.Host\EditorServicesHost.cs

PowerShell Editor Services Host v0.12.0.0 starting (pid 7700)...

 Host application details:

   Name:      Visual Studio Code Host
   ProfileId: Microsoft.VSCode
   Version:   1.0.0
   Arch:      64-bit

 Operating system details:

    Version: Microsoft Windows NT 10.0.14393.0
    Arch:    64-bit

6/04/2017 8:30:49 AM [NORMAL] - Method "Initialize" at line 214 of C:\projects\powershelleditorservices\src\PowerShellEditorServices\Session\PowerShellContext.cs

PowerShell runtime version: 5.1.14393.953, edition: Desktop

6/04/2017 8:30:50 AM [NORMAL] - Method "FindPSScriptAnalyzerModule" at line 261 of C:\projects\powershelleditorservices\src\PowerShellEditorServices\Analysis\AnalysisService.cs

PSScriptAnalyzer found at C:\Users\bewhite\.vscode\extensions\ms-vscode.PowerShell-0.12.1\modules\PSScriptAnalyzer\PSScriptAnalyzer.psd1

6/04/2017 8:30:51 AM [NORMAL] - Method "StartLanguageService" at line 158 of C:\projects\powershelleditorservices\src\PowerShellEditorServices.Host\EditorServicesHost.cs

Language service started, listening on port 14818

6/04/2017 8:30:51 AM [NORMAL] - Method "StartDebugService" at line 213 of C:\projects\powershelleditorservices\src\PowerShellEditorServices.Host\EditorServicesHost.cs

Debug service started, listening on port 21345

@daviwil
Copy link
Contributor

daviwil commented Apr 5, 2017

Thanks @BernieWhite! Your logs look clean, but perhaps we're missing some context without Verbose logs turned on. Can you turn on verbose logs and try it again?

https://github.com/PowerShell/vscode-powershell#2-capture-verbose-logs-and-send-them-to-us

Judging from what I see here, the language server fully starts up but maybe there's some problem preventing the integrated console from showing the initial prompt.

@daviwil daviwil modified the milestones: Next Patch Update, Next Feature Update Apr 6, 2017
@daviwil daviwil modified the milestones: April 2017, May 2017 May 8, 2017
@claudiospizzi
Copy link

claudiospizzi commented May 29, 2017

Hi David

Same issue on my system. If I start Visual Studio Code with the PowerShell extension when I'm completely offline, like in the train, the PowerShell host is starting forever:
image

This are the log files with verbose turned on:
EditorServices.txt
vscode-powershell.txt

I can see that the PowerShell Editor Service is listening on 127.0.0.1:23623
image

And the good old telnet to the local port 23623 works too. So no localhost network issue.

@daviwil daviwil modified the milestones: May 2017, June 2017 Jun 1, 2017
@daviwil daviwil modified the milestones: June 2017, July 2017 Jul 11, 2017
@giordyb
Copy link

giordyb commented Oct 21, 2017

I'm having the same issue, is there anything I can do to help troubleshooting this?

@daviwil daviwil modified the milestones: July 2017, Future Oct 26, 2017
@TylerLeonhardt
Copy link
Member

This should be fixed in #1327 since we are no longer relying on TCP sockets in the extension.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug: VS Code Bugs in VS Code itself. Issue-Bug A bug to squash.
Projects
None yet
Development

No branches or pull requests

6 participants