.NET Core 2.1.6 + EF Core in Azure , memory leak issues
up vote
0
down vote
favorite
We are currently running a backend application in Azure, which is running on .NET core 2.16 (windows), and uses EF Core with SQL database in Azure. At the moment we are experiencing a slow increase in memory usage which seems related to the number of API calls. After performing a memory dump i noticed that there are a lot of Objects of 'Microsoft.Extensions.Caching.Memory.CacheEntry', i am thinking there must be a memory leak occurring or GC is not working properly.
I made a screenshot of the dump, i am curious if anyone has any ideas about this, is this a problem related to the current .net Core version or do i need to investigate more in the EF queries and general configuration?
.net

New contributor
Jos Eilers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
We are currently running a backend application in Azure, which is running on .NET core 2.16 (windows), and uses EF Core with SQL database in Azure. At the moment we are experiencing a slow increase in memory usage which seems related to the number of API calls. After performing a memory dump i noticed that there are a lot of Objects of 'Microsoft.Extensions.Caching.Memory.CacheEntry', i am thinking there must be a memory leak occurring or GC is not working properly.
I made a screenshot of the dump, i am curious if anyone has any ideas about this, is this a problem related to the current .net Core version or do i need to investigate more in the EF queries and general configuration?
.net

New contributor
Jos Eilers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
We are currently running a backend application in Azure, which is running on .NET core 2.16 (windows), and uses EF Core with SQL database in Azure. At the moment we are experiencing a slow increase in memory usage which seems related to the number of API calls. After performing a memory dump i noticed that there are a lot of Objects of 'Microsoft.Extensions.Caching.Memory.CacheEntry', i am thinking there must be a memory leak occurring or GC is not working properly.
I made a screenshot of the dump, i am curious if anyone has any ideas about this, is this a problem related to the current .net Core version or do i need to investigate more in the EF queries and general configuration?
.net

New contributor
Jos Eilers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
We are currently running a backend application in Azure, which is running on .NET core 2.16 (windows), and uses EF Core with SQL database in Azure. At the moment we are experiencing a slow increase in memory usage which seems related to the number of API calls. After performing a memory dump i noticed that there are a lot of Objects of 'Microsoft.Extensions.Caching.Memory.CacheEntry', i am thinking there must be a memory leak occurring or GC is not working properly.
I made a screenshot of the dump, i am curious if anyone has any ideas about this, is this a problem related to the current .net Core version or do i need to investigate more in the EF queries and general configuration?
.net

.net

New contributor
Jos Eilers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jos Eilers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jos Eilers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 5 hours ago


Jos Eilers
1
1
New contributor
Jos Eilers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Jos Eilers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Jos Eilers is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Jos Eilers is a new contributor. Be nice, and check out our Code of Conduct.
Jos Eilers is a new contributor. Be nice, and check out our Code of Conduct.
Jos Eilers is a new contributor. Be nice, and check out our Code of Conduct.
Jos Eilers is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53371407%2fnet-core-2-1-6-ef-core-in-azure-memory-leak-issues%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown