PowerShell / PowerShell/vscode-powershell
Process-arrow not showing after breakpoint
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.9k
- Forks
- 547
- PR merge metrics
- No merged PRs in 30d
Description

Issue Type: Bug
Tried to search the issuses both in VS-code and Powershell but could not find this problem.
After a breakpoint is hit, the "Process-arrow" in the taskarea is not shown when continuing the execution (F5).
Don't know if this is just in Powershell or if it is in VS Code itself.
A simple example:
Add Breakpoint at both Write-host
start debug (F5) and you see the "Process-arrow" in the orange taskarea
After the first breakpoint is hit, press F5 to continue
The "Process-arrow" do not show in the orange taskarea (see attached image)
For me that makes it hard to know if the code is still executing or if it is frozen/hung.
for ($i = 0; $i -lt 10000; $i++) {
write-host $i
if ($i -eq 3758) {
#add breakpoint here
Write-Host "Breakpoint Here"
}
if ($i -eq 6823) {
#add breakpoint here
Write-Host "Breakpoint Here"
}
}
Extension version: 1.9.0
VS Code version: Code 1.28.1 (3368db6750222d319c851f6d90eb619d886e08f5, 2018-10-11T18:13:53.910Z)
OS version: Windows_NT x64 10.0.17134
System Info
| Item | Value |
|---|---|
| CPUs | Intel(R) Core(TM) i7-6650U CPU @ 2.20GHz (4 x 2208) |
| 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 video_decode: enabled video_encode: enabled webgl: enabled webgl2: enabled |
| Memory (System) | 15.93GB (8.72GB free) |
| Process Argv | |
| Screen Reader | no |
| VM | 0% |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the reported loop in VS Code with the PowerShell extension, using breakpoints at both Write-Host statements and continuing with F5. Start by tracing the debugger status and process-arrow update after continuing; done means the process arrow remains visible while execution continues, and the behavior is covered by a regression test if the existing test structure identifies a suitable location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- powershell, typescript, vscode
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100