ASP.NET: Out of memory issue

Hello Folks,

I've a website which accessible on intranet.

From last week, I got errors of "Out of memory" issue once load on website.
1. Total user of website around 350
2. Concurrent users 50

The errors like
> "Insufficient memory to continue the execution of the program"
> "Exception of type 'System.OutOfMemoryException' was thrown"

Please note, no changes have been made from last two months on production website.

Do you have thoughts, what are the main cause to need to focus to resolve this?

Best Regards,
Mohit Pandit
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

ITsolutionWizardConnect With a Mentor Commented:
Your asp net source codes may have some database activities and database connection does not close and end up having memory leaks ....
David Johnson, CD, MVPConnect With a Mentor OwnerCommented:
First determine what your private memory usage is for the apppool.  How much memory is available for IIS? You might need to add more memory.

As a work-around you can recycle the apppool when it reaches a certain size before you get the out of memory error. Session Variables will be lost.

    Open IIS Manager. In the Connections pane, expand the server node and click Application Pools.  On the Application Pools page, select an application pool, and then click Recycling in the Actions pane. Select Private memory usage (in KB), and in the corresponding box type a memory value at which you want the application pool to recycle.  Click Next, select the events that should be logged when an application pool recycles, and then click Finish.
He mentioned no changes last two months so iis should not been related. Maybe check it is because the size of database may be increased or query end up running complex and more steps ....
Never miss a deadline with

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

käµfm³d 👽Commented:
You should run a profiler against your application and perform a load test. This should reveal memory leaks in your application.
Assuming it is an error on the web server, it could also be an infinite loop, perhaps introduced by new data or lack thereof.
MohitPanditAuthor Commented:
Okay, I'll look into memory leak & let you know
MohitPanditAuthor Commented:
Do you know, any tool to identify memory leak on production website?

Best Regards
Daniel Van Der WerkenIndependent ConsultantCommented:
Does rebooting the server or restarting the IIS process fix the problem? I'm curious because if the restart solves the problem, at least temporarily, then I think that a memory leak might be the problem.

Not 100% for sure, but I believe that if the issue is resolved, temporarily at least, by a restart, that indicates a leak is a possible problem.

A simple web search shows a couple of articles for how-to regarding detecting leaks.
MohitPanditAuthor Commented:
@Daniel, yes restart IIS solves problem temporarily.
I am digging into source code & find-out root cause. I'll get informed you all.
MohitPanditAuthor Commented:
All Courses

From novice to tech pro — start learning today.