You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
The IO::managers map is added to, but never removed from, and there is no method to clear it - so a bunch of stuff leaks.
To Reproduce
Use LeakCanary to watch OkHttpClient instances passed into IO::Options.callFactory / webSocketFactory - after IO.socket.close() - those OkHttpClient will leak, being held by IO::managers - which is added to, but is never cleared.
Socket.IO java client version: 2.1.0
Expected behavior
Either automatically remove entries from IO::managers when sockets are closed, or provide a method to clear IO::managers map - and release the resources held by it.
Platform:
Device: Pixel 4a
OS: Android 13
The text was updated successfully, but these errors were encountered:
Describe the bug
The
IO::managers
map is added to, but never removed from, and there is no method to clear it - so a bunch of stuff leaks.To Reproduce
Use LeakCanary to watch
OkHttpClient
instances passed intoIO::Options.callFactory
/webSocketFactory
- afterIO.socket.close()
- thoseOkHttpClient
will leak, being held byIO::managers
- which is added to, but is never cleared.Socket.IO java client version:
2.1.0
Expected behavior
Either automatically remove entries from
IO::managers
when sockets are closed, or provide a method to clearIO::managers
map - and release the resources held by it.Platform:
The text was updated successfully, but these errors were encountered: