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

Intellisense Hanging in Editor #2590

Closed
GHartsfield opened this issue Mar 28, 2020 · 10 comments
Closed

Intellisense Hanging in Editor #2590

GHartsfield opened this issue Mar 28, 2020 · 10 comments
Labels
Area-IntelliSense Issue-Bug A bug to squash. Resolution-Fixed Will close automatically.

Comments

@GHartsfield
Copy link

Issue Type: Bug

As of today when I updated to 2020.3.1 there have been frequent intellisense hangs/crashes. I cannot seem to find a way to reproduce it reliably but it happens within a few minutes of reloading either the extension or vscode. Had been working consistently for about a week on the same project in the previous extension version with no issues. No other changes to the environment. Attached the error logs and editor services verbose output.

Extension version: 2020.3.1
VS Code version: Code 1.43.2 (0ba0ca52957102ca3527cf479571617f0de6ed50, 2020-03-24T07:38:38.248Z)
OS version: Windows_NT x64 10.0.18363

System Info
Item Value
CPUs Intel(R) Core(TM) i5-3350P CPU @ 3.10GHz (4 x 3100)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: enabled
skia_renderer: disabled_off_ok
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off_ok
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 31.95GB (21.95GB free)
Process Argv
Screen Reader no
VM 0%

editorServices.txt
1585437259-3a5b48de-f50f-46cc-9d7c-3cd4c1d40cee1585436631396.zip

@ghost ghost added the Needs: Triage Maintainer attention needed! label Mar 28, 2020
@TylerLeonhardt
Copy link
Member

Thanks for the info! Can you please set the log level to Diagnostic and try to repro again? It looks like the log files in the zip are basically empty... I expected to see more if they were proper logs. This might be an indication that the issue could be elsewhere but we need to know more.

"powershell.developer.editorServicesLogLevel": "Diagnostic"

@TylerLeonhardt TylerLeonhardt added Needs-Repro-Info and removed Needs: Triage Maintainer attention needed! labels Mar 30, 2020
@GHartsfield
Copy link
Author

Thanks for the reply, I thought there wasn't much in the logs as well - unfortunately those were taken in diagnostic mode. I have switched back over to the non-preview extension and the problem has gone away. Don't know if its relevant but I am using custom prefixes in the modules which your GetCommandSynopsisAsync refactor seemed to fix - now that I'm back in non-preview I have no intellisense issues but I do have issues with the module prefixes again.

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Mar 30, 2020
@stevenebutler
Copy link

My intellisense doesn't work at all with the latest preview 2020.3.1, anywhere in my code base. I have dropped back to 2020.3.0 where it appears to work reasonably well.

@TylerLeonhardt
Copy link
Member

@stevenebutler @GHartsfield I just published 2020.3.2 of PowerShell Preview. Can you give it a try and let me know how works for you? Thanks!

@TylerLeonhardt
Copy link
Member

This is fixed in PowerShell/PowerShellEditorServices#1248

@TylerLeonhardt TylerLeonhardt added Resolution-Fixed Will close automatically. and removed Needs-Repro-Info labels Apr 1, 2020
@TylerLeonhardt
Copy link
Member

I've received one report that said this issue was fixed so I'm going to close this. Let me know how it goes for you two!

@stevenebutler
Copy link

Hi yes, is fixed for me too - I did give a thumbs up to indicate this but you may not have seen it.

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Apr 1, 2020
@TylerLeonhardt
Copy link
Member

@stevenebutler thanks! Sorry I wasn't sure if that was "it's fixed! " or "I'll try it out!" my bad.

@TylerLeonhardt TylerLeonhardt removed the Needs: Maintainer Attention Maintainer attention needed! label Apr 1, 2020
@GHartsfield
Copy link
Author

It appears I'm still having issues with this. It happens much less often (after a few hours rather than minutes). But I still can't seem to reliably reproduce it. Have attached new diagnostic log. The intellisense hang happened around 2:10pm.

2020.3.2.zip

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Apr 2, 2020
@stevenebutler
Copy link

Hi, I see similar lock ups with the editor intellisense after a period of it working. I'm sorry I'm unable to provide logs due to my employment agreement. A restart of the integrated console gets it working again so it's annoying but not completely detrimental.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-IntelliSense Issue-Bug A bug to squash. Resolution-Fixed Will close automatically.
Projects
None yet
Development

No branches or pull requests

4 participants