-
Notifications
You must be signed in to change notification settings - Fork 495
Closed
Labels
bugThis issue is a bug.This issue is a bug.closed-for-stalenessmodule/lambda-client-libneeds-reproductionThis issue needs reproduction.This issue needs reproduction.response-requestedWaiting on additional info and feedback. Will move to close soon in 7 days.Waiting on additional info and feedback. Will move to close soon in 7 days.
Description
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
bradlis7
Metadata
Metadata
Assignees
Labels
bugThis issue is a bug.This issue is a bug.closed-for-stalenessmodule/lambda-client-libneeds-reproductionThis issue needs reproduction.This issue needs reproduction.response-requestedWaiting on additional info and feedback. Will move to close soon in 7 days.Waiting on additional info and feedback. Will move to close soon in 7 days.
