Any news on this issue?
Em 26/12/2012 10:38, Felipe Farinon escreveu:
No, the C++ wrapper calls the ZMQ functions directly, no heap allocation
involved. The Event handle's that are leaking are make_fdpair's fault.
As you said you runned your C code with valgrind I assume that you have
runned
On Wed, Jan 2, 2013 at 12:14 PM, Felipe Farinon
felipe.fari...@powersyslab.com wrote:
Any news on this issue?
It got resolved in libzmq master:
https://github.com/zeromq/libzmq/pull/489- Pieter mentioned he was
backporting to 3.2, so try pulling from GH and
see if it resolves your issue.
Ian
Yes, issue solved. Thanks.
Em 02/01/2013 11:31, Ian Barber escreveu:
On Wed, Jan 2, 2013 at 12:14 PM, Felipe Farinon
felipe.fari...@powersyslab.com
mailto:felipe.fari...@powersyslab.com wrote:
Any news on this issue?
It got resolved in libzmq master:
No, the C++ wrapper calls the ZMQ functions directly, no heap allocation
involved. The Event handle's that are leaking are make_fdpair's fault.
As you said you runned your C code with valgrind I assume that you have
runned it in a Linux. The leak only reproduces on Windows, as the leaky
piece
When I run the same code in C, with valgrind, I don't see any memory
leaks. Does the C++ runtime not use the heap?
#include czmq.h
int main (void)
{
zctx_t *ctx = zctx_new ();
int i;
for (i = 0; i 1000; ++i) {
void *front = zsocket_new (ctx, ZMQ_PAIR);
void *back =
I'm using version 3.2.2 of ZeroMQ, running on a Windows 7, compiled with
a MSVC 10.
The following piece of code reproduces the problem:
http://pastebin.com/6p2sLaEM
It seems that if we create lots of PAIR sockets in Windows, we get an
event leak. The event leak is shown by this image, taken at
