I recently tracked down a memory leak of the message memory buffer related
to disconnecting sockets. Github issue here:
https://github.com/zeromq/libzmq/issues/1313
The problem stemmed from not calling msg::close on a message that fails to
write to the pipe. While researching through the code I no
Haha be careful Thomas or you will wake Pieter :)
Well I am mixing socket operations binds/connects with opening and
closing files (and reading and writing from/to files).
I also use ZMQ to poll on my files' descriptors. So at first sight it
doesn't look like a ZMQ bug.
I see two things to try:
>
> At least in the C++ version, the problem is relatively fragile
I always see the problem in my pure-C test
There are those that maintain that C is a simpler and more robust language
than C++ :-)~
On Tue, Jan 20, 2015 at 11:32 AM, Olaf Mandel
wrote:
> Hello,
>
> Am 20.01.2015 18:07, schri
Hello,
Am 20.01.2015 18:07, schrieb Arnaud Kapp:
> I don't really see anything in the small example that could cause a bug.
> I am myself using libzmq (with zmqpp as a wrapper) on a Raspberry Pi +
> a Piface digital card (which is a SPI device), and I have no trouble.
>
At least in the C++ versio
Hello,
I don't really see anything in the small example that could cause a bug.
I am myself using libzmq (with zmqpp as a wrapper) on a Raspberry Pi +
a Piface digital card (which is a SPI device), and I have no trouble.
My kernel version is 3.12.28+ and I use a recent (a few commits behind
HEAD)
I'm running your sample against current libzmq trunk, Ubuntu 14.04 and I am
unable to reproduce any leak.
On Tue, Jan 20, 2015 at 2:08 AM, Pieter Hintjens wrote:
> OK, thanks for the simple test case.
>
> I'm not familiar enough with the internals of libzmq to debug this. I
> see that tcp_connec
No, not really. libc++ doesn't do anything particularly interesting with
fd's but I just wanted to formally rule it out.
Unfortunately I don't have a system (or any experience dealing) with SPI
devices. I don't think libzmq does anything particularly 'funky' with any
of the file descriptors it mana
Hello Thomas,
thank you for the quick answer.
Am 20.01.2015 15:11, schrieb Thomas Rodgers:
> Do you see the same behavior if you replace C with fopen() ?
-Snipp-
Not quite: if the error occurs, the behaviour is the same as before. But
now the error _always_ happens: closing the file descriptor i
Do you see the same behavior if you replace C with fopen() ?
On Tue, Jan 20, 2015 at 7:40 AM, Olaf Mandel
wrote:
> Am 20.01.2015 14:35, schrieb Olaf Mandel:
> -Snipp-
> >
> >
> > #include
> > #include
> -Snipp-
>
> Shoot: That was missing a few include statements at the top the program
> and t
Am 20.01.2015 14:35, schrieb Olaf Mandel:
-Snipp-
>
>
> #include
> #include
-Snipp-
Shoot: That was missing a few include statements at the top the program
and the compile instructions. Correct start of the demo program:
/*
* Compile with:
* g++ -Wall -Werror -Wextra -o test test.cpp -lz
Hello,
I was trying to use ZMQ in a C++ program that also uses the STL to open
regular files and that uses the open(2) and ioctl(2) syscalls of the
Linux kernel for SPI communication (on an ARM platform). For certain
combinations of opening and closing a regular file and binding to a TCP
or Inproc
OK, thanks for the simple test case.
I'm not familiar enough with the internals of libzmq to debug this. I
see that tcp_connecter.cpp is closing the socket if it can't resolve
the hostname. However it's possible some error handling isn't right
here.
On Tue, Jan 20, 2015 at 5:04 AM, Tomas Krajca
12 matches
Mail list logo
