Open jzmf opened 4 years ago
Maybe the "meory leak" is related to multiple SendAsync() without closing the socket? A SendAsync always ends with listening for more data and I suspect it has som lifetime. Another SendAsync will assume socket is brand new and configure yet another send/receive session.
Just a hint from discoveries in #2
Have you tested the application for memory leaks? I used the library in my console application and after each reading of data from the mbus device via TCP communication, the memory occupancy increases by about 2 kB. According to a debugger in VS2017, the problem is somewhere in SocketAsyncEventArgs Valley.Net.Bindings ...
JM