-
Notifications
You must be signed in to change notification settings - Fork 52
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
MaxListenersExceededWarning: Possible EventEmitter memory leak detected #54
Comments
What did you do to make this happen? |
when source url expired,this problem happened! |
I am having exactly the same problem for the first time since using this project: (node:11900) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 finish listeners added. Use emitter.setMaxListeners() to increase limit Signal starts jumping... |
#46 someone else reported it too |
How many sources do you have? Does the error go away if you reduce the amount of sources configured? |
I am testing just that, 2 sources, everything is okay. Seems to be more of a problem with HLS sources?? More info in a while. Will add 20 sources. |
got 29 channels running and it is working with no issue, with TS Inputs. |
after 1 hour, i am getting again: (node:110284) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unpipe listeners added. Use emitter.setMaxListeners() to increase limit |
OK, i found that some of my sources were giving 404 and that was causing the jumps. |
To debug enable -v on the proxy and see what error msg is ffmpeg yelling. |
Is this still an issue? |
(node:29078) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 unpipe listeners added. Use emitter.setMaxListeners() to increase limit
The text was updated successfully, but these errors were encountered: