.NET Core 2.1.6 + EF Core in Azure , memory leak issues
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
add a comment |
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
You need to analyze the dump and find out why instances of CacheEntry are still in memory. Then analyzing the code of classes you discovered during dump analysis need to understand what goes wrong.
– Ed.ward
Nov 20 '18 at 13:31
add a comment |
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
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
asked Nov 19 '18 at 9:13
Jos EilersJos Eilers
1
1
You need to analyze the dump and find out why instances of CacheEntry are still in memory. Then analyzing the code of classes you discovered during dump analysis need to understand what goes wrong.
– Ed.ward
Nov 20 '18 at 13:31
add a comment |
You need to analyze the dump and find out why instances of CacheEntry are still in memory. Then analyzing the code of classes you discovered during dump analysis need to understand what goes wrong.
– Ed.ward
Nov 20 '18 at 13:31
You need to analyze the dump and find out why instances of CacheEntry are still in memory. Then analyzing the code of classes you discovered during dump analysis need to understand what goes wrong.
– Ed.ward
Nov 20 '18 at 13:31
You need to analyze the dump and find out why instances of CacheEntry are still in memory. Then analyzing the code of classes you discovered during dump analysis need to understand what goes wrong.
– Ed.ward
Nov 20 '18 at 13:31
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
You need to analyze the dump and find out why instances of CacheEntry are still in memory. Then analyzing the code of classes you discovered during dump analysis need to understand what goes wrong.
– Ed.ward
Nov 20 '18 at 13:31