Reply to thread

Message: <blockquote data-quote="HAneo" data-source="post: 28090979" data-attributes="member: 17432">[USER=318958]@wpmanoj[/USER]Ok, i did some modifications to the Code. removed the While Listening. and implement Callbacks. this way we don't have to wait for the requests but we will be notified upon the request hits the context. and it's Async Now. you can have multiple requests at the same time [CODE]public void NonblockingListener(){        _listener = new HttpListener();        _listener.Prefixes.Add("http://localhost/asynctest/");        _listener.AuthenticationSchemes = AuthenticationSchemes.Anonymous;        _listener.Start();        _listener.BeginGetContext(OnContext, null);        Console.ReadLine(); }[/CODE][CODE]   private void OnContext(IAsyncResult ar)    {        try        {            var guid = Guid.NewGuid();            var ctx = _listener.EndGetContext(ar);            _listener.BeginGetContext(OnContext, null);            Console.WriteLine(DateTime.UtcNow.ToString("HH:mm:ss.fff") + " Handling request");            var buf = Encoding.ASCII.GetBytes("Hello world - " + guid.ToString());            ctx.Response.ContentType = "text/plain";            ctx.Response.OutputStream.Write(buf, 0, buf.Length);            ctx.Response.OutputStream.Close();            Console.WriteLine(DateTime.UtcNow.ToString("HH:mm:ss.fff") + " completed");        }        catch (Exception ex)        {            Console.WriteLine(DateTime.UtcNow.ToString("HH:mm:ss.fff") + " Error " + ex.Message);        }    }[/CODE]Now even with this change, I couldn't stop the memory from increasing. See this.<img src="https://i.postimg.cc/y6JqHSNp/Mem-Profile1.png" alt="" class="fr-fic fr-dii fr-draggable " style="" />Then I analyze what has happened.  you can see where the increase or decrease happens(analysis 2 snapshots and see the difference)<img src="https://i.postimg.cc/28wgdd96/Mem-Profile2.png" alt="" class="fr-fic fr-dii fr-draggable " style="" />So the Root of the problem is above 1 and 2. these both cause a memory leak. and as per the MS words, you cannot do anything about this. they always leaking a few Bytes per request. if logic gets complex this may leak from bytes to KB easily.  you cannot do anything to this. because these are the .NET Runtime and OS API calls. both of them are in the Unmanaged stack which you or I never can access.  Read these articles <a href="https://social.msdn.microsoft.com/Forums/vstudio/en-US/068ac24e-1ede-47d6-8ef8-9aee73eed4ab/memory-leak-involving-systemreflectionruntimemodule?forum=netfxbcl" target="_blank">https://social.msdn.microsoft.com/Forums/vstudio/en-US/068ac24e-1ede-47d6-8ef8-9aee73eed4ab/memory-leak-involving-systemreflectionruntimemodule?forum=netfxbcl</a><a href="https://docs.microsoft.com/en-us/dotnet/core/diagnostics/debug-memory-leak" target="_blank">https://docs.microsoft.com/en-us/dotnet/core/diagnostics/debug-memory-leak</a></blockquote>

Verification: Hathara warak wissa keeyada? (Hathara wadi karanna 20)

Top Bottom