asked on asp.net suspected memory leak issue
Hi,
We are having a asp.net application deployed on windows 2008 server.
The users are not able to log in to the application all of a sudden. It stays on the login page forever without logging in.
I checked perfmon.exe.
I added counters for private bytes, bytes in all heaps and # current logical threads.
bytes in all heaps and current logical threads remain steady.
I do not see anything for private bytes counter.
Why does it not show any line in for this counter? What does it mean?
if bytes in all heaps remains constant, it might not be a managed memory issue. The problem might be with the unmanaged memory.
How do i detect this issue?
In the asp.net debug mode(development machine), can i see if any objects are not disposed?
Thanks
We are having a asp.net application deployed on windows 2008 server.
The users are not able to log in to the application all of a sudden. It stays on the login page forever without logging in.
I checked perfmon.exe.
I added counters for private bytes, bytes in all heaps and # current logical threads.
bytes in all heaps and current logical threads remain steady.
I do not see anything for private bytes counter.
Why does it not show any line in for this counter? What does it mean?
if bytes in all heaps remains constant, it might not be a managed memory issue. The problem might be with the unmanaged memory.
How do i detect this issue?
In the asp.net debug mode(development machine), can i see if any objects are not disposed?
Thanks
ASP.NET
Last Comment
Stephan
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
Low disk space can be an issue, it mostly depends on what your application does on how it will react to it.
Here you find a list of counters you can use that will help:
http://msdn.microsoft.com/en-us/library/x2tyfybc(v=vs.110).aspx
http://msdn.microsoft.com/en-us/library/ekec01h3(v=vs.110).aspx
http://msdn.microsoft.com/en-us/library/9tyc2s04(v=vs.110).aspx
Here you find a list of counters you can use that will help:
http://msdn.microsoft.com/en-us/library/x2tyfybc(v=vs.110).aspx
http://msdn.microsoft.com/en-us/library/ekec01h3(v=vs.110).aspx
http://msdn.microsoft.com/en-us/library/9tyc2s04(v=vs.110).aspx
After a restart of the server and recycle of application pools, our application is running.
I am using performance monitor and added a few counters
privatebytes, bytes in all heaps, arrival rate, requests/sec, # of exceptions thrown per sec etc.
Before restart, we made 2 changes
First change was removing some parts of code which we suspected were causing issues.
Second - our server had only 2 GB of hard disk space left. We cleared lots of log files and some backup files.
After restart of the server, the application started to run good.
Is the low disk space a reason for the issue which we experienced? If yes, why did it not affect our other applications which were hosted on the same server?
Do you suggest any other counters in addition to the above mentioned counters that i added to performance monitor? I want to continue monitoring this application for a few weeks.
Thanks