-
|
I'm trying Aspire for the first time and found the During writing there was a peak (marked), and after that the memory usage increases more slow. While the Visual Studio process memory shows a different value (but stable): In the Task Manager I can see the ASP.NET process memory increasing steady, too: You can find the whole project source here ( I run the micro service (without Aspire) on a Debian Linux, too, where the memory usage stays stable since a few hours now. Now I'm wondering - do I have a memory leak somewhere in my development environment, or does is come from Aspire? Is it a problem or normal operation? UPDATE: After watching this for maybe one hour, there seemed to be some garbage collection, Maybe it was only some cache or buffer filling up data. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
It's unlikely aspire is making your process memory leak. Instead, it's just making you aware of it (if it's even a leak that is). I recommend docs on diagnosing a memory leak in order to get a better understanding. It's also likely that this could be a side effect of using server GC being on by default in ASP.NET Core projects and uses more memory. I also recommend looking at the GC counters to get a better understanding beyond high level process memory counters. |
Beta Was this translation helpful? Give feedback.



It's unlikely aspire is making your process memory leak. Instead, it's just making you aware of it (if it's even a leak that is). I recommend docs on diagnosing a memory leak in order to get a better understanding.
It's also likely that this could be a side effect of using server GC being on by default in ASP.NET Core projects and uses more memory. I also recommend looking at the GC counters to get a better understanding beyond high level process memory counters.