Will memory get over-used?

[=?Utf-8?B?eWtmZmM=?=]

Some codes instantiate an Arraylist and add many many objects to the list
before the code start to process the items and kill the object. (I assume
this could be a bad approach and I will need to find ways to improve the
design/performance)

But the question is: will this going to kill my system due to memory
overflow or something? I wonder if VB.net is designed to save my Arraylist
"contents" onto virtual memory (disk) once its size reaches certain limit.

Thank you.

[Tom]

I can't vouch for the first question, but the second, i can give a 99%
positive of NO. It won't kill your system. Windows manages the Swap
Memory, not the .Net framework, and so if needed, it will page it (And
increase the page file to the maximum size if it ever got that big!)

ykffc wrote:

Some codes instantiate an Arraylist and add many many objects to the list
before the code start to process the items and kill the object. (I assume
this could be a bad approach and I will need to find ways to improve the
design/performance)

But the question is: will this going to kill my system due to memory
overflow or something? I wonder if VB.net is designed to save my Arraylist
"contents" onto virtual memory (disk) once its size reaches certain limit.

Thank you.

[Michel Posseth [MCP]]

Wel probabaly your app run into an error before the windows max is reached
as an object running on the framework can only use about 2 gig of memory

"ykffc" <yk***@discussions.microsoft.comschreef in bericht
news:65**********************************@microsof t.com...

Some codes instantiate an Arraylist and add many many objects to the list
before the code start to process the items and kill the object. (I assume
this could be a bad approach and I will need to find ways to improve the
design/performance)

But the question is: will this going to kill my system due to memory
overflow or something? I wonder if VB.net is designed to save my
Arraylist
"contents" onto virtual memory (disk) once its size reaches certain limit.

Thank you.

[Robert]

Each *ITEM* in an arraylist is limited to 2GB..

Wel probabaly your app run into an error before the windows max is
reached as an object running on the framework can only use about 2 gig of
memory

>Some codes instantiate an Arraylist and add many many objects to the list
before the code start to process the items and kill the object. (I
assume
this could be a bad approach and I will need to find ways to improve the
design/performance)

But the question is: will this going to kill my system due to memory
overflow or something? I wonder if VB.net is designed to save my
Arraylist
"contents" onto virtual memory (disk) once its size reaches certain
limit.

[Michel Posseth [MCP]]

there is currently a 2GB limit for all CLR objects, no matter what OS
you are running on 32 / 64 bit.
There is also a practical limit, dependent on the current system
conditions, (memory fragmentation ) that limits the growth to the largest
continguous block of memory available.
http://msdn2.microsoft.com/en-us/lib...64(VS.80).aspx
http://blogs.msdn.com/joshwil/archiv...10/450202.aspx
Please not the following even on a 64 bit system the object limit is 2 GB
so
however if the system has enough ram you can alocate multiple objects of 2
gb
on a 32 bit system you cannot allocate full 2 gb so there sure is an
advantage to have a 64 bit system and to compile in 64 bit modus

Michel

"Robert" <[e-mail] in bericht
news:Oe**************@TK2MSFTNGP05.phx.gbl...

>
Each *ITEM* in an arraylist is limited to 2GB..

>Wel probabaly your app run into an error before the windows max is
reached as an object running on the framework can only use about 2 gig of
memory

>>Some codes instantiate an Arraylist and add many many objects to the
list
before the code start to process the items and kill the object. (I
assume
this could be a bad approach and I will need to find ways to improve the
design/performance)

But the question is: will this going to kill my system due to memory
overflow or something? I wonder if VB.net is designed to save my
Arraylist
"contents" onto virtual memory (disk) once its size reaches certain
limit.