-
Notifications
You must be signed in to change notification settings - Fork 29.8k
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
_http_server / TLSSocket : MaxListenersExceededWarning #20352
Comments
Can you start node with |
Sure thing
|
@radixxko not sure if it's a problem but the screenshot above seems to expose a password. |
Thanks for the warning @lpinca, credentials are used just for the testing purposes so no issue there |
I can't reproduce, this is my test case with a self signed certificate. const cluster = require('cluster');
const fs = require('fs');
const https = require('https');
if (cluster.isMaster) {
cluster.fork();
cluster.fork();
} else {
const server = https.createServer({
cert: fs.readFileSync('certificate.pem'),
key: fs.readFileSync('key.pem')
});
server.on('request', function (req, res) {
res.end('Hello');
});
server.listen(8080);
} |
Seeing there's been no reproduction, I'm going to close this out. Thanks anyway for the report. |
Hello after using simple https server forked into 2 child processes via node native cluster module we are getting MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 error listeners added. warning
Minimal code where the issue is present:
The issue is present in v10.0.0 node version as well it is replicable in 9.x version.
Funny thing is that we are getting MaxListenersExceededWarning every few seconds even if there are no clients connecting to server.
Any hints?
The text was updated successfully, but these errors were encountered: