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
Libzmq (4.3.1) has been crashing with memory corruption/stack overflows in zmq_proxy. We've updated to 4.3.4 to hopefully help mitigate, but long term we should move away from a libraries written in C.
Potentially Redis? Some other pubsub? Ideally we can get rid of the dual zmq/redis dependency at the same time, and just use a single fast-but-safe pubsub.
The text was updated successfully, but these errors were encountered:
Libzmq (4.3.1) has been crashing with memory corruption/stack overflows in zmq_proxy. We've updated to 4.3.4 to hopefully help mitigate, but long term we should move away from a libraries written in C.
Potentially Redis? Some other pubsub? Ideally we can get rid of the dual zmq/redis dependency at the same time, and just use a single fast-but-safe pubsub.
The text was updated successfully, but these errors were encountered: