I have a web.api in .net core 3.1 that continually receives byte array data. I have noticed that after a dozen of calls, the memory suddenly increases with +100Mb.
As you can see in the GIF, the memory increases steadily as the calls are being handled. And then at 155Mb, the memory increases to 296Mb.
I have created a repo: https://github.com/puppetSpace/MemoryIssue This contains a client project, that calls the API continually. And the web.api project, that gets the byte array from the body and waits 500ms (simulate work). I just want to know a couple of things:
- Is someone else also getting this result?
- Is this normal behavior? like it's reserving memory? Or it's just because of debbuging?
I tried to use a profiler, but I can't figure out what causes the sudden increase.
I also asked this on stack overflow, but I think I'm gonna get a better answer here: https://stackoverflow.com/questions/62138833/net-core-web-api-sudden-memory-peak-after-dozen-of-calls/62144292#62144292