Closed alexrobin closed 3 years ago
It seems the issue is caused by a reference to the websocket session that is not nullified on close
Alex. Does this affect how we should develop drivers or does it seem to be confined to core?
No impact on drivers. It's confined to core (SOS impl). Mathieu is working on a fix.
The memory leak appears when using the WebSocket service only. After investigation, we see that the listener of Jetty maintains a reference to the SOSWebSocketOut object which prevents it from being GC.
and updating Jetty to version 9.4.42.v20210604, the memory leak has gone.
The solution is simply to update Jetty
Super. Good job. How might have this issue manifested itself in the server and in the COP?
A memory leak becomes quickly visible when issuing many websocket requests. It impacts v1.4 and maybe v2.0