PUSH socket overflows

Question

PUSH socket overflows

cc32d9 opened this issue 6 years ago · comments

I'm developing this module using AZMQ, and it doesn't go well:
https://github.com/EOSChronicleProject/eos-chronicle/blob/81dbe977a264fcf674d95ef941a5479ef30f78bc/chronicle-receiver/exp_zmq_plugin.cpp

the data is written quite intensively with async_send, and it's not limited by high watermark like the synchronous socket would do. If there's no recipient attaching to that socket, the sender keeps sending endlessly. As soon as the recipient connects to the socket, the sender bails out with "Cannot allocate memory" exception.

Why is it not limited by HWM? I would assume it should do it like the traditional ZMQ library does.

Thomas Rodgers · Answer 1 · Tue Apr 23 2019 06:08:34 GMT+0800 (China Standard Time)

Is there any chance I could get a minimal reproduction case?

cc32d9 · Answer 2 · Tue Apr 23 2019 06:15:27 GMT+0800 (China Standard Time)

well in the meanwhile I dropped the idea of supporting ZMQ, and now using websockets only.

But the reproduction case should be quite easy to build, just send to ASMQ socket in an endless loop and you will see it.