Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Net Core 3.0 Memory #41978

Closed
Alan-Lun opened this issue Oct 22, 2019 · 2 comments

Comments

@Alan-Lun
Copy link

@Alan-Lun Alan-Lun commented Oct 22, 2019

#41669
記憶體都持續飆高,不會下降釋放
基本專案
https://github.com/Alan-Lun/NetCoreMemory

圖片
init
https://imgur.com/PgpjVFe
呼叫一次
https://imgur.com/2w25aUI
連續呼叫
https://imgur.com/SU8bWQm
https://imgur.com/t3GxpGY

目前專案上Memory
Quartz.net(https://github.com/quartznet/quartznet)
https://imgur.com/IyanjhX
.Net Core 3.0 WebAPI
https://imgur.com/YXBCd2e

memory total: 128mb
build image: mcr.microsoft.com/dotnet/core/sdk:3.0-buster
dotnet publish API.csproj -c Release -r linux-x64 --self-contained true

run image: mcr.microsoft.com/dotnet/core/aspnet:3.0-buster-slim

AWS ECS
CPU available:2048
Memory available(MB)
Agent version: 1.29.0
Docker version:18.06.1-ce

@danmosemsft

This comment has been minimized.

Copy link
Member

@danmosemsft danmosemsft commented Oct 22, 2019

This is an ASP.NET project. I also see some Autofac, Microsoft.Extensions.* etc. I suggest to move this issue to https://github.com/aspnet/AspNetCore

@Alan-Lun have you tried reducing the repro case? Ie., removing components and functionality to make your app as simple as possible until the repro stops happening? This will often suggest the issue, or at least make it easier to figure out the issue.

Also, in this repo the community generally works in English language. Is it possible for you to work this way?

@Alan-Lun

This comment has been minimized.

Copy link
Author

@Alan-Lun Alan-Lun commented Oct 23, 2019

OK,Sorry
Next time I will translate it first and then post it.

Can you help me the last time? Thank you.


aspnet/AspNetCore#14932
mkArtakMSFT
Thanks @Alan-Lun.
It seems there's already investigation happening on the corefx repo. Not to duplicate the effort, we're closing this issue. If it turns out that the problem is caused by ASP.NET Core, @danmosemsft will transfer the issue from corefx to here and we'll use the transferred issue instead.

@Alan-Lun Alan-Lun closed this Nov 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants
You can’t perform that action at this time.