Open
Description
Hi, I have update the aws libs from 3.7 to 3.8. After the update my webserver crash with
@smithy/node-http-handler: WARN - socket usage at capacity=50 and 1956 additional requests are enqueued.
See https://docs.aws.amazon.com/sdk-for-javascript/v3/developer-guide/node-configuring-maxsockets.html
or increase socketAcquisitionWarningTimeout=(millis) in the NodeHttpHandler config.
<--- Last few GCs --->
[7:0x4353e000] 7082600 ms: Mark-Compact 251.7 (257.2) -> 251.0 (257.5) MB, pooled: 1 MB, 213.92 / 0.07 ms (average mu = 0.102, current mu = 0.057) allocation failure; scavenge might not succeed
[7:0x4353e000] 7082825 ms: Mark-Compact 252.0 (257.5) -> 250.7 (257.5) MB, pooled: 1 MB, 217.80 / 0.10 ms (average mu = 0.069, current mu = 0.033) allocation failure; scavenge might not succeed
<--- JS stacktrace --->
FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
1: 0xe98a91 node::OOMErrorHandler(char const*, v8::OOMDetails const&)
2: 0x12a74f0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&)
3: 0x12a788c v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&)
It seem the 3.8 version don't close the connections
I don't know what libs cause this error, but never happen with 3.7
SDK version number
{
"@aws-sdk/client-dynamodb": "^3.806.0",
"@aws-sdk/client-iam": "^3.806.0",
"@aws-sdk/client-s3": "^3.806.0",
"@aws-sdk/client-ses": "^3.806.0",
"@aws-sdk/client-sqs": "^3.806.0",
"@aws-sdk/client-sts": "^3.806.0",
"@aws-sdk/cloudfront-signer": "^3.775.0",
"@aws-sdk/lib-dynamodb": "^3.806.0",
"@aws-sdk/lib-storage": "^3.806.0",
"@aws-sdk/s3-request-presigner": "^3.806.0"
}Which JavaScript Runtime is this issue in?
NodeJS 23