Thanks
I found if I closed down VS.NET, and then open again, I can get the routine
to run ok - this together with running the routine with a smaller set of
data without exception confirms it's not a loop problem. However, subsequent
running of the routine produces the problem again. It's like .NET can't
allocate memory fast enough. Perhaps because it's switching from RAM to
Virtual Memory. When the routine is run for the first time, slightly less
memory is used. It's like .NET won't allocate/release memory fast enough the
'next time' around.
"Andrew Christiansen" <no-spam> wrote in message
news:ea**************@TK2MSFTNGP10.phx.gbl...
I've expierienced this problem in VB6... Don't really know why this
occurs, but maybe its VB's way of saying a memory request has been denied for some
weird reason. I've found restarting the computer to solve the problem.
Andrew
"harry" <harry@nospam> wrote in message
news:%2****************@TK2MSFTNGP10.phx.gbl... VS.NET 2002 (VB.NET) on Win XP.
Is there a known bug regarding .NET reporting
System.OutOfMemoryException when there is plenty of Virtual memory available?
My TaskManager shows 1237M / 2181M in use. Even the peak memory usage of
1391MB is nowhere near the limit.
I have 1.15GB physical memory ... remainder is System allocated Virtual
Memory / Swap Space.
Is this a bug or am I misunderstanding something?
Thanks
Harry