Saúl Ibarra Corretgé
Saúl Ibarra Corretgé
Sure thing!
It's a known issue, we haven't gotten around fixing it yet :-/
It's alas not possible to do so deterministically, but you can try to leave the meeting in the applicationWillTerminate delegate method. Here is an example: https://github.com/jitsi/jitsi-meet/blob/532b5858c55e0d4c772edcb8369a2c2c8baaee64/ios/app/src/AppDelegate.m#L62
What inotify limits do you have?
Can you please create a standalone test case that exhibits the problem? To be clear, these are not leaks, you are just creating too many resolvers. Not sure how much...
> My rough understanding from the existing issues on this is that this creates a race condition where you end up opening more before the last ones are fully closed...
That's no longer the case, I fixed that in pycares by waiting for all queries in the channel to end. The actual destruction happens in a different thread, so that's...
Here is a possible idea, but I'm not a huge fan of it, because it hides the real problem, aka people creating tons of resolvers for no reason: cache the...
New arch is not currently supported.
Closing since the RN version must match the one we are using.