Forum Discussion
Solved
Why is my ASP.Net Web API piling up memory?
Hi everyone, I have a very simple MVC web api with a single controller that currently does nothing but returning a value. I am publishing it in VS2022 Preview 1 into a single file, so I get an .e...
- If you're calling it ever 250ms, it's likely not quiet enough for the Garbage collector to fire up. And with 90mb, it likely isn't pushing enough memory pressure (that's still tiny) to force the Garbage collector.
Have you tried launching it without debugger? Maybe with dotnet run command. Is the behaviour same even then?
If you're calling it ever 250ms, it's likely not quiet enough for the Garbage collector to fire up. And with 90mb, it likely isn't pushing enough memory pressure (that's still tiny) to force the Garbage collector.
- Ok, I have to apologize and row back here. Even though I called GC.Collect(), I just noticed that I was running an older build that did NOT call the garbage collection. Running the latest build does indeed get rid of the memory piling.
So thanks for the help! This resolves my issue. 🙂 Thanks. That was also my initial thought, so I was calling GC.Collect() at the end of each request (i.e. before return 0;), simply to force the gc to free all generations but...no change and no memory freed. RAM still piling up. 😕
It seems strange that this does not happen when running the API in debug mode from inside of VS. This gives me the impression that it might not be the API itself maybe? Maybe it's how I spawn the process (doing this from C++ via Qt and QProcess).- Hmm, even if I start the API manually (double-clicking the executable), this memory piling occurs. So it's not due to the process spawning itself either.
