"Out of memory"

I have a rather large script, that performs several hundred Get-WmiObject
against various servers. Usually Get-WmiObject "Win32_Process" with various
filters.

Sometimes the script returns a "out of memory" error. But not always.

How can this best be handled in PowerShell ?

--
Jakob Bindslet

Is it possible to split the script up into smaller pieces.
--
Richard Siddaway

Please note that all scripts are supplied "as is" and with no warranty


"Jakob Bindslet" wrote:

> I have a rather large script, that performs several hundred Get-WmiObject
> against various servers. Usually Get-WmiObject "Win32_Process" with various
> filters.
>
> Sometimes the script returns a "out of memory" error. But not always.
>
> How can this best be handled in PowerShell ?
>
> --
> Jakob Bindslet
>
>

On Wed, 3 Jan 2007 05:17:00 -0800, RichS
<RichS@discussions.microsoft.com> wrote:

>Is it possible to split the script up into smaller pieces.

It would be possible, but I'd rather not.

I'm not even sure if the error occurs in PowerShell on in WMI - I've
been digging a bit into $error, but none of the properties gives me
ant insight into this matter.

--
Jakob Bindslet

Do you generate a new object for each WMI call.

could try setting a trap

trap [OutofMemoryException]{........

--
Richard Siddaway

Please note that all scripts are supplied "as is" and with no warranty


"Jakob Bindslet" wrote:

> On Wed, 3 Jan 2007 05:17:00 -0800, RichS
> <RichS@discussions.microsoft.com> wrote:
>
> >Is it possible to split the script up into smaller pieces.
>
> It would be possible, but I'd rather not.
>
> I'm not even sure if the error occurs in PowerShell on in WMI - I've
> been digging a bit into $error, but none of the properties gives me
> ant insight into this matter.
>
> --
> Jakob Bindslet
>
>
>