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

[Preview-2020.2.0] F5 works only once #2488

Closed
ili101 opened this issue Feb 23, 2020 · 7 comments · Fixed by PowerShell/PowerShellEditorServices#1210
Closed

[Preview-2020.2.0] F5 works only once #2488

ili101 opened this issue Feb 23, 2020 · 7 comments · Fixed by PowerShell/PowerShellEditorServices#1210
Labels
Area-Debugging Issue-Bug A bug to squash. Resolution-Fixed Will close automatically.
Milestone

Comments

@ili101
Copy link

ili101 commented Feb 23, 2020

Issue Type: Bug

Setup:

Preview-2020.2.0 + PS7
(Do not create launch.json)

Steps to reproduce:

  1. F5 (file will run)
  2. F5 (debugger will start and do nothing)

F5
EditorServices.log
Extension version: 2020.2.0
VS Code version: Code 1.42.1 (c47d83b293181d9be64f27ff093689e8e7aed054, 2020-02-11T14:45:59.656Z)
OS version: Windows_NT x64 10.0.18363

System Info
Item Value
CPUs AMD Ryzen 7 1800X Eight-Core Processor (4 x 3593)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
metal: disabled_off
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
protected_video_decode: unavailable_off
rasterization: unavailable_off
skia_renderer: disabled_off
surface_control: disabled_off
surface_synchronization: enabled_on
video_decode: enabled
viz_display_compositor: enabled_on
viz_hit_test_surface_layer: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) undefined
Memory (System) 4.00GB (1.57GB free)
Process Argv
Screen Reader no
VM 100%
@ghost ghost added the Needs: Triage Maintainer attention needed! label Feb 23, 2020
@TylerLeonhardt
Copy link
Member

TylerLeonhardt commented Feb 24, 2020

@ili101 do you have any workspace open?

I've tried this on PS6 and PS7 and can't repro the behavior you're seeing. The only difference right now is that I'm on macOS and you're on Windows.

Also as a troubleshooting step, if you hit enter in the console before hitting F5 a second time, does that work?

@TylerLeonhardt TylerLeonhardt added Needs-Repro-Info and removed Needs: Triage Maintainer attention needed! labels Feb 24, 2020
@ili101
Copy link
Author

ili101 commented Feb 24, 2020

It happens with and without workspace.
I tested it only on windows.
Hitting enter or Ctrl+C between F5s actually prevent the problem.
Maybe another clue after the second F5 if I F6 to pause it stops on a temporary AppData\Local\Temp\PSES-2376\[ILI] Script Listing.ps1 script with only 0 in it.

@ghost ghost added the Needs: Maintainer Attention Maintainer attention needed! label Feb 24, 2020
@rjmholt rjmholt added this to the 2.0.0 milestone Feb 24, 2020
@TylerLeonhardt
Copy link
Member

That's really great information @ili101. Thank you!

@SydneyhSmith SydneyhSmith added Area-Debugging Issue-Bug A bug to squash. and removed Needs-Repro-Info Needs: Maintainer Attention Maintainer attention needed! labels Feb 25, 2020
@TylerLeonhardt
Copy link
Member

I was unable to repro this on Windows, however, I did reproduce this on @SydneyhSmith 's machine.

It seems to happen when a machine is totally bogged down and so the PowerShell extension runs very slowly and gets into some bad state.

Still investigating...

@TylerLeonhardt
Copy link
Member

I'm able to reproduce when I comment out my personal changes to the prompt function.

@rjmholt
Copy link
Contributor

rjmholt commented Feb 26, 2020

This seems to have the same root cause as #2364

@DarkLite1
Copy link

I think I'm having the same issue. The code never finishes execution and the debug pop-up at the top stays. Quitting it is not always possible, so I'm forced to kill the terminal and restart it. It might be related but code unfolding is also no longer possible in some cases. Thank you for looking in to this nasty little bug.

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

Successfully merging a pull request may close this issue.

5 participants