Artur Pietrzyk

This do not make sense to merge it as it will be replaced again with the openapi generator on the next change. Good to see that the fix was merged...

This is aborted?

Ping.

 @mvburgh Did you made any progress since then on that?

 Code which causing this is very simple just the PublisherSocker who had connected ~10 subscribers:  I'm not sure it's the same bug as the initial bug was related...

@somdoron I confirm that Linger is equal to the {00:00:00} at the end of the Start() function in the snippet provided above @(Start(): return port;) publisher.Options {NetMQ.SocketOptions} Affinity: 0 Backlog:...

@somdoron Take a look at the incoming reference chart.  In my use-case, the subscribers should not come and go frequently, but there could be a bug on my side...

I'm using the 4.0.0.239-pre version.

@somdoron No problem, I actually found interesting fact - the leak is visible only on nodes on which there is no communication activity between Publisher and Subscriber (silence), it's ok...

 It looks like the Pipe is also referenced to the Pub+Sub, however, I don't know it's the same instance.