-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Flooding requests results in memory leak #43548
Comments
/cc @nodejs/http |
@ShogunPanda Thank you! |
Hi, exist fix for node 16.x? Regards |
@nodejs/tsc I'm still not an expert of how our backporting strategy works, but I assume since 16 LTS it will only receive critical and security updates. Am I right? If that's the case, then @cesarjorgemartinez there will be no backport of this. |
It seems unlikely we'll get that fix in v18.x as it breaks express and Koa. |
@ShogunPanda, https://github.com/nodejs/release#release-phases possibly has information regarding the backporting strategy that you may find useful. (Note that there's a distinction between Active LTS and maintenance, so it is possible to get non-critical updates and features in Active LTS lines.) |
@BethGriggs Thanks, highly appreciated. I'll take a look to it very soon! |
Hi,
Hum, very strange, because I detect this supervising multiple attacks
inside our apps using flooding. The express also must be work using this
LTS version 18 that you comment, I planning to upgrade to 18.
Regards,
CJ
El lun., 1 ago. 2022 18:27, Paolo Insogna ***@***.***>
escribió:
… @nodejs/tsc <https://github.com/orgs/nodejs/teams/tsc> I'm still not an
expert of how our backporting strategy works, but I assume since 16 LTS it
will only receive critical and security updates. Am I right?
If that's the case, then @cesarjorgemartinez
<https://github.com/cesarjorgemartinez> there will be no backport of this.
—
Reply to this email directly, view it on GitHub
<#43548 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AA5N2CLQ4NHIYUBDPEGP56TVW73IFANCNFSM5ZU5BTSA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
PR-URL: #43587 Fixes: #43548 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ricky Zhou <[email protected]> Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
PR-URL: #43587 Fixes: #43548 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ricky Zhou <[email protected]> Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
PR-URL: #43587 Fixes: #43548 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ricky Zhou <[email protected]> Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
PR-URL: #43587 Fixes: #43548 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ricky Zhou <[email protected]> Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
PR-URL: nodejs#43587 Fixes: nodejs#43548 Reviewed-By: Matteo Collina <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Ricky Zhou <[email protected]> Reviewed-By: Mohammed Keyvanzadeh <[email protected]>
Version
v16.15.1
Platform
Linux DNSBox 5.15.0-39-generic #42-Ubuntu SMP Thu Jun 9 23:42:32 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Subsystem
HTTP
What steps will reproduce the bug?
1. Run the code below using
node
without requiring any additional dependencies2. Use this site to stress-test the server using the following configuration below.
How often does it reproduce? Is there a required condition?
You might have to run the test twice for it to take effect but you have to wait for the current test to finish before sending another one. After all of the tests are complete, the server will get a lot of
MaxListenersExceededWarning
errors and will eventually crash because it will reach the memory limit.What is the expected behavior?
It shouldn't show a memory leak error and should just continue the requests as normal.
What do you see instead?
Additional information
Source
The text was updated successfully, but these errors were encountered: