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
warning: possible EventEmitter memory leak detected. 11 listeners added. Use emitter.setMaxListeners() to increase limit. #565
Comments
Could you post full logs? |
|
I am not seeing this in my testing. Why does everything say raven.js and the line numbers don't really make sense. Do you have some custom code that could be causing this? |
I'm using Sentry for logging which uses raven and that's where raven.js and line 55 are coming from. If I disable Sentry I still get the same error and instead of raven it's |
New event listeners were internally added to SIP.js for the Transport work, so that could definitely explain why you are seeing it. And that is what we were trying to determine. That being said, it is just a warning and if the number is not growing out of control, it can safely be ignored. @JimGreenberg will investigate increasing this limit within SIP.js so that the warnings will disappear in a future release. Alternatively, you could submit a PR to resolve this. Thanks |
Upon further investigation and increasing the listener count, I found that there might indeed be an issue with ever growing listeners. In |
Yeah, this seems related to the transport work. We moved some of the responsibilities over to individual components, and the issue you're seeing probably is related. I'm going to get a patch out for this hopefully by monday or tuesday. Huge thanks for spending the time to track this down. |
This is fixed in 0.11.1+ |
After switching to 0.11.0 I am now getting a possible EventEmitter memory leak error in the console. Here is the trace that is provided with the error:
From Firefox:
From Chrome:
This happens when I un-hold a call. Please let me know if there's more information I can provide.
The text was updated successfully, but these errors were encountered: