-
Notifications
You must be signed in to change notification settings - Fork 657
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
@grpc/gprc-js: EventEmitter leak for drain/close/error #916
Comments
I'm really going to need a stack trace or reproduction code to track this down. We can get stack traces using this code snippet from #694: process.on('warning', e => console.warn(e.stack)); |
@murgatroid99 I'm trying to reproduce it again, it appears to be harder to do so than before. Will let you know when I have a stack trace for you. |
There it is. I still need to run some extra tests to understand the conditions in which this happens. I'm not sure if this can happen in normal conditions or if it has anything to do with unreliable internet / suspending the machine. |
Those call stacks don't say grpc-js anywhere. I don't think this one is actually a grpc-js issue. |
I'll see if I can repro this. This might be an issue in Firestore. |
I am not able to come up with a test case, but this seems to be happening in our Watch code. On re-connect, we pipe back to the original stream. I suspect that this is happening when we have more than 10 reconnect attempts. I am closing this issue for now - will resolve this as part of googleapis/nodejs-firestore#661 |
See googleapis/nodejs-firestore#661 (comment)
Firestore customers (on
@grpc/grpc-js 0.4.3) are reporting that they are still seeing EventEmitter leak warnings, albeit not for
connectivityStateChanged` listeners.Instead, they see:
The text was updated successfully, but these errors were encountered: