Normal
This has been discussed a few times before already and is to do with the way dot net handles memory.When code no longer needs memory in DotNet it marks it as unneeded.To increase efficiency and speed, the DotNet garbage collector monitors system memory and keeps that memory in a virtual "recycle bin" until it's either needed again by the code or if needed by other applications the memory is released.Basically this is how Windows XP handles memory. Everything gets more than it needs as long as there is plenty to go around. There is only a problem if this is happening and your system has not enough memory (which should never be the case if the garbage collector is working poperly).
This has been discussed a few times before already and is to do with the way dot net handles memory.
When code no longer needs memory in DotNet it marks it as unneeded.
To increase efficiency and speed, the DotNet garbage collector monitors system memory and keeps that memory in a virtual "recycle bin" until it's either needed again by the code or if needed by other applications the memory is released.
Basically this is how Windows XP handles memory. Everything gets more than it needs as long as there is plenty to go around. There is only a problem if this is happening and your system has not enough memory (which should never be the case if the garbage collector is working poperly).
