Marina
Thu Nov 10 12:25:38 CST 2005
That is if the objects are eligible for GC to begin with. It is possible
that you have objects that are not going out of scope for a long time.
One example of this is if you are storing large amounts of data in Session
state, and you have long session timeouts. So that data hangs around for a
long time before it is eligible for GC, and after you get a lot of users on
the system, you just run out of space.
That is one example.
Another thing to try is to use a different server. If the same problem is
there, then it is more likely that the problem is with the application. If
the other server works fine under the same load, then it would be something
specific to the first machine's configuration.
"Nick K." <nickkka52@yahoo.com> wrote in message
news:%23r4%23Kwh5FHA.3588@TK2MSFTNGP15.phx.gbl...
>I am considering all possibilities. I asked if there were any unmanaged
>code being called and I was told no. Garbage collecting is something .Net
>is suppose to handle automatically.
>
> "Marina" <someone@nospam.com> wrote in message
> news:e%23oJ7Xh5FHA.1140@tk2msftngp13.phx.gbl...
>> Is it possible there are resources that are not being cleaned up
>> properly, and are thus not being garbage collected?
>>
>> "Nick K." <nickkka52@yahoo.com> wrote in message
>> news:%23TPkozg5FHA.472@TK2MSFTNGP15.phx.gbl...
>>> We have ASP.Net web applications running on a Windows 200 Server using
>>> the .Net Framework 1.0. We have been experiencing out of memory errors
>>> being displayed on the web page after the application runs for sometimes
>>> days.
>>>
>>> I have attempted to adjust the settings in the machine.config file
>>> setting the <processModel> memoryLimit attribute up from the default 60
>>> (%) to 80(%). Around this same time we upped the memory on this server
>>> to 4 Gig.
>>>
>>> The application seemed to run for longer before getting the
>>> out-of-memory errors, but they still happen before we have to re-boot
>>> the server.
>>>
>>> Should this memoryLimit be bumped up even more? Are there other
>>> attributes in the <processModel> that should be adjusted that would
>>> help? How do we go about tracking down what is taking up all the memory?
>>>
>>
>>
>
>