Skip to content

When open Powershell files, it crashes #1848

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

Closed
w-Yuan opened this issue Apr 5, 2019 · 7 comments
Closed

When open Powershell files, it crashes #1848

w-Yuan opened this issue Apr 5, 2019 · 7 comments

Comments

@w-Yuan
Copy link

w-Yuan commented Apr 5, 2019

Issue Type: Bug

Go to a folder and try to open a powershell files. It crashes and asks for reopen or close.

Extension version: 1.12.0
VS Code version: Code 1.33.0 (0dd516dd412d42323fc3464531b1c715d51c4c1a, 2019-04-04T15:14:46.685Z)
OS version: Windows_NT ia32 10.0.18356

System Info
Item Value
CPUs Intel(R) Xeon(R) CPU E5-1660 v3 @ 3.00GHz (16 x 2993)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 31.92GB (16.88GB free)
Process Argv analog\Input\Eyes\Tools\ETN
Screen Reader no
VM 0%
@TylerLeonhardt
Copy link
Member

Thanks for the info! Can you also attach the logs here so we can get a better idea of what's going on?

@Tadimsky
Copy link

Tadimsky commented Apr 5, 2019

I'm having the same issue.
I attached my logs here - it doesn't look like it has much of interest though.

logs.zip

@w-Yuan
Copy link
Author

w-Yuan commented Apr 6, 2019

logs.zip

Hope this will be helpful. If enable powershell extension, I will not be able to open VSCode as it keeps crashing.

@hypercube33
Copy link

hypercube33 commented Apr 9, 2019

Mine is doing this now too - looks like it parses functions and inserts a line above to have the information for references to the function, then the line disappears, then the extension crashes.

If I open a new ps1 file and don't have anything, and add some code it seems to be OK.

Edit - "[powershell]": {
"editor.codeLens": false

Fixes the issue but reduces functionality

@TylerLeonhardt
Copy link
Member

Are any of you opening files/folders with UNC paths?

@hypercube33
Copy link

I specifically am working on files that sit on a unc path almost exclusively.

@TylerLeonhardt
Copy link
Member

That's being tracked with #1830
Fixed in PowerShell/PowerShellEditorServices#908

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants