Web application use too much memory

Question

On my host company, i have 2, more or less identical, .net applications. This two applications use the same pool, which has a max memory on 300 mb.

I can refresh the startpage for one of the application about 10 times, then i get a out of memory exception and the pool is crashed.

In my application i print out this memory values:
PrivateMemorySize64: 197 804.00 kb (193.00 mb)
PeakPagedMemorySize64: 247 220.00 kb (241.00 mb)
VirtualMemorySize64: 27 327 128.00 kb (26 686.00 mb)
PagedMemorySize64: 197 804.00 kb (193.00 mb)
PagedSystemMemorySize64: 415.00 kb (0.00 mb)
PeakWorkingSet64: 109 196.00 kb (106.00 mb)
WorkingSet64: 61 196.00 kb (59.00 mb)
GC.GetTotalMemory(true): 2 960.00 kb (2.00 mb)
GC.GetTotalMemory(false): 2 968.00 kb (2.00 mb)

I have read, and read and read an seen videos about memory profiling, but i can't find any problem when i do the profiling of my application. I use ANTS Memory profiler 8 and get this result when i refresh the startpage one time after the build:

When i look at the Summary, .NET is using 41.65 MB of 135.8 MB total private bytes allocated for the application. This values gets bigger and bigger for each refresh. Is that normal? When i refresh 8 times i get this: .NET is using 56.11 MB of 153 MB total private bytes allocated for the application.

Where should i start? What could be the problem that use so much memory? Is 300 mb to low for memory?

It all depends on what your code is doing. Make sure you're calling Dispose on everything. If you have database connections, ensure you close those in your Dispose chain. — krillgar
– krillgar, Commented Mar 26, 2014 at 18:53

Haney · Accepted Answer · 2014-03-26 18:58:03Z

1

This is undoubtedly due to a memory leak in your code, likely in the form of not disposing/closing connections to something like a queue or database. Profiling aside, review your code and ensure that you're closing/disposing all appropriate resources: your problem should then relieve itself.

answered Mar 26, 2014 at 18:58

Haney

35.2k9 gold badges61 silver badges71 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

mrcode · Accepted Answer · 2014-03-27 12:23:54Z

0

There was some db connections that not was disposed. Then i have a class which removes Etags, like this:

public class CustomHeaderModule : IHttpModule
{
    public void Dispose() { }

    public void Init(HttpApplication context)
    {
        context.PreSendRequestHeaders += OnPreSendRequestHeaders;
    }

    void OnPreSendRequestHeaders(object sender, EventArgs e)
    {
        HttpContext.Current.Response.Headers.Remove("ETag");
    }
}'

Must i remove the new event i add in the Init function? Or will the GC fix that?

And i have a lot of this:

Task.Factory.StartNew(() =>
{
   Add(...);
});

But i don't dispose them in my code. Will the GC fix that or should i do on a other way?

edited Mar 27, 2014 at 12:23

answered Mar 27, 2014 at 8:38

mrcode

5672 gold badges6 silver badges19 bronze badges

1 Comment

Jan 'splite' K. Over a year ago

I know I am necromanting this, but for random googlers: no, GC will not magically fix any leak. GC (this is oversimplification! But I think good enough to grasp the concept of GC...) only mark unreachable objects (this.p = new Person(); this.p = null; - that new instance of Person is now unreachable) as free memory (btw but not in OS, C# will hog memory for further use). Calling Dispose() should release stuff like this Person, so they can be marked for GC. If you forget to call Dispose(), stuff are still reachable and will not be marked for GC -> you have memory leak.

Collectives™ on Stack Overflow

Web application use too much memory

2 Answers 2

Comments

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related