C#•2y ago

✅ Growing memory issues for ASP.NET Core App

I'm using JetBrians Rider's memory profiler. I found that my application memory growing significantly. The app pretty much pulls stock market's candlestick data, cache it via

MemoryCache

MemoryCache

with SlidingExpiration of 10 minute and AbsoluteExpiration of 1 hour. That's pretty much where I think most of the memory goes to.

From the profiling image below, I found that the heap generation is taking lots of space. I searched onlline and found that I should call

GC.Collect()

GC.Collect()

GC.Collect()

GC.Collect() to retain memory. But this stackoverflow post says otherwise.

What can I do to improve the memory usage of my application? What kind of things do I need to look for in order to make it consume less memory?

Stack Overflow

What's so wrong about using GC.Collect()?

Although I do understand the serious implications of playing with this function (or at least that's what I think), I fail to see why it's becoming one of these things that respectable programmers w...

Jimmacle•1/22/24, 1:36 AM

use the view that shows you which objects are allocated

Jimmacle•1/22/24, 1:36 AM

it's correct that you generally don't want to call GC.Collect(), the GC runs automatically and if you have a memory leak calling that won't fix it anyway

Jimmacle•1/22/24, 1:38 AM

the most likely issue is that you're holding references to objects you aren't actually using anymore and preventing them from being collected