-
Notifications
You must be signed in to change notification settings - Fork 64
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
possible EventEmitter memory leak #44
Comments
Thanks for reporting! I will have a look at this as soon as possible (although I cannot promise when). |
I'm unable to reproduce this. uCSS only creates two event emitters itself. But I see that Request has several issues mentioning EventEmitter memory leaks. I've tried updating to the newest version of Request, hoping that it fixes the problem. Could you please check if the problem persists? If this still is a problem, it may be because of a redirect loop. Setting maxRedirects in the options when doing request.get (lib/css.js and lib/html.js) may help. I would be grateful if you could try this, or provide me with the config you use so that I can reproduce and investigate further. Thanks! |
Did you, by any chance, get the warning when running tests? |
@oyvindeh I was getting the error when using ucss on a large complex site, I am still seeing these warnings, possibly in conjunction with timeouts
|
Yup I can confirm this. I think this might be shown in new version of Node. |
I'm seeing a lot of:
(node) warning: possible EventEmitter memory leak detected. 11 end listeners added. Use emitter.setMaxListeners() to increase limit.
. Is this a real concern?The text was updated successfully, but these errors were encountered: