Vscode-powershell: Console crash when pasting parameter

Created on 28 Dec 2018  路  6Comments  路  Source: PowerShell/vscode-powershell

Issue Type: Bug

  1. Create a new Untitled-1 Doc (PowerShell)
  2. paste this code
function Test-Params
{
    Param(
        $Param1,
        $Param2
    )
}
Test-Params -Param1
  1. Copy "Param2"
  2. paste it over "Param1" (in the line Test-Params -Param1)
    (if it's not crashing the first time repeat with "Param2")
  3. crash...

error

Extension version: 1.10.2
VS Code version: Code 1.30.1 (dea8705087adb1b5e5ae1d9123278e178656186a, 2018-12-18T18:12:07.165Z)
OS version: Windows_NT x64 10.0.17134

EditorServices.log


System Info

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 1800X Eight-Core Processor (16 x 3593)|
|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.95GB (8.26GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|


Area-Integrated Console Issue-Bug

Most helpful comment

I'm closing this since we believe it to be fixed. @ili101 you can re-open it if you still see this bug with 1.11.0.

All 6 comments

I can confirm the same behaviour with PS Core 6.1.0 and 6.1.1.

PS Extension version: 1.10.2
VSCode 1.30.1

Thanks for submitting this. I have a fix I'll be submitting shortly. It might be a few weeks until there is a release though. In the meantime, if you don't use an untitled file then you shouldn't run into this bug.

Thanks Keith.,
The workaround works for me.
Just save the file, even as Untitled-1.ps1 , and the console stops crashing after paste operation.

Yeah, it is not the name per-se, it is that it is an "in-memory" document with no file backing it.

I believe this bug to be fixed by the PR referenced above. The fix should be available in 1.11.0. Should we wait for confirmation of the fix before closing this?

I'm closing this since we believe it to be fixed. @ili101 you can re-open it if you still see this bug with 1.11.0.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

lukegriffith picture lukegriffith  路  3Comments

timoline picture timoline  路  3Comments

daviwil picture daviwil  路  4Comments

CJHarmath picture CJHarmath  路  3Comments

pcgeek86 picture pcgeek86  路  4Comments