-
Notifications
You must be signed in to change notification settings - Fork 477
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
DOTNET_GCHeapHardLimit is still needed with .NET 8 #1699
Comments
I'm not sure whether it's related or not, but we use DataDog Lambda extensions: |
Needs review with the team. |
Reference issue dotnet/runtime#83563 |
I was under the impression that it affects ECS only, no? |
Norm wrote a blog post about this last year, it mentions Lambda as well: https://aws.amazon.com/blogs/developer/configuring-net-garbage-collection-for-amazon-ecs-and-aws-lambda/ |
@dscpinheiro |
i am experiencing out of memory errors even with DOTNET_GCHeapHardLimit 0x20000000
here is also an example where it throws out of memory even with max memory used 360MB
|
@Dreamescaper Good afternoon. Please advise if it is possible to share sample code and steps for reproduction. |
This issue has not received a response in 5 days. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled. |
we are holding back on moving to .net 8 from .net 6 until we can understand more why out of memory errors are happening on all services we have migrated |
@ashishdhingra |
@Dreamescaper or anybody else having this issue would it be possible to share your What I want to make sure is if your function is bring in its own version of |
This issue has not received a response in 5 days. If you want to keep this issue open, please just leave a comment below and auto-close will be canceled. |
We encountered a similar problem and setting |
Describe the bug
I was investigating rare OutOfMemory issues with our lambdas. I've tried to re-add DOTNET_GCHeapHardLimit environment variable, which I've removed after an update to .NET 8. And it does seem to fix the issue, even though I was under the impression that it's not required anymore with .NET 8.
Expected Behavior
Lambdas shouldn't fail with OutOfMemory issues without any additional steps.
Current Behavior
Lambdas still fail with OutOfMemory exceptions, unless DOTNET_GCHeapHardLimit env var is set.
Additional Information/Context
Here's a plot of Memory Usage before and after DOTNET_GCHeapHardLimit variable was set. You can see that RAM usage doesn't get as close to 512MB after env var is added.
Targeted .NET Platform
.NET 8
Operating System and version
AmazonLinux
The text was updated successfully, but these errors were encountered: