Quiting a ps1 script when an error occurs

I've got a PSH prompt open, and have called a .ps1 script. It contains an
error.

It seemingly loops forever, and if I Ctrl-C it stops.

That's fine and all, but the script seems to hold on to files it
reads/writes:
PS C:\> gc 1.csv|select-object -first 1
Get-Content : The process cannot access the file 'C:\1.csv' because it is
being used by another process.
At line:1 char:3
+ gc <<<< 1.csv|select-object -first 1

Only way I know out is to kill the PSH prompt and open a new one.

There must be a better way?

Marco

Marco Shaw wrote:
> I've got a PSH prompt open, and have called a .ps1 script. It contains an
> error.
>
> It seemingly loops forever, and if I Ctrl-C it stops.
>
> That's fine and all, but the script seems to hold on to files it
> reads/writes:
> PS C:\> gc 1.csv|select-object -first 1
> Get-Content : The process cannot access the file 'C:\1.csv' because it is
> being used by another process.
> At line:1 char:3
> + gc <<<< 1.csv|select-object -first 1
>
> Only way I know out is to kill the PSH prompt and open a new one.
>
> There must be a better way?
>
> Marco

Mmmm... that seems like a pretty bad bug. Terminated pipelines should
be terminated, not still holding open file handles. I guess it's a bit
trickier given that there's no automatic cleanup for threads, only
processes, and PowerShell runs pipelines in threads.

Hi Marco,

> That's fine and all, but the script seems to hold on to files it
> reads/writes:
> PS C:\> gc 1.csv|select-object -first 1
> Get-Content : The process cannot access the file 'C:\1.csv' because it is
> being used by another process.
> At line:1 char:3
> + gc <<<< 1.csv|select-object -first 1
>
> Only way I know out is to kill the PSH prompt and open a new one.

What happens when you enter

PS C:\> [GC]::Collect(); [GC]::WaitForPendingFinalizers()

a few times? Are the files still locked?

cu

Max

On Nov 9, 5:39 am, Maximilian Hänel <ngS...@smjh.de> wrote:
> Hi Marco,
>
> > That's fine and all, but the script seems to hold on to files it
> > reads/writes:
> > PS C:\> gc 1.csv|select-object -first 1
> > Get-Content : The process cannot access the file 'C:\1.csv' because it is
> > being used by another process.
> > At line:1 char:3
> > + gc <<<< 1.csv|select-object -first 1
>
> > Only way I know out is to kill the PSH prompt and open a new one.What happens when you enter
>
> PS C:\> [GC]::Collect(); [GC]::WaitForPendingFinalizers()
>
> a few times? Are the files still locked?

This works for me if I do something like:

> (gi "foo.txt").Open([System.IO.FileMode]"Open")
CanRead : True
[... goodness ...]

> (gi "foo.txt").Open([System.IO.FileMode]"Open")
Exception calling "Open" with "1" argument(s): "The process cannot
access the file 'C:\users\jam\repos\foo.txt' because it is being
used by another process."
[... badness ...]

> [GC]::Collect(); [GC]::WaitForPendingFinalizers()

> $f.open([System.IO.FileMode]"Open")
CanRead : True
[... goodness ...]

> What happens when you enter
>
> PS C:\> [GC]::Collect(); [GC]::WaitForPendingFinalizers()
>
> a few times? Are the files still locked?

I fixed my problem, so there's no lock for me to test anymore. I'll
research what you're telling me above. Looks like something useful in case
I get in trouble again.

"Jason Mobarak" <jason.mobarak@gmail.com> wrote in message
news:1163118105.449805.314680@m7g2000cwm.googlegroups.com...
On Nov 9, 5:39 am, Maximilian Hänel <ngS...@smjh.de> wrote:

> PS C:\> [GC]::Collect(); [GC]::WaitForPendingFinalizers()

That's a good line to be remembered for, Jason.