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
Summary: When utilizing a zloop from within a thread spawned by zthread valgrind claims that some blocks are possibly lost and some are still reachable. The problem only occurs if you start the zloop.
Notes: The example isn't exactly the most sensible thing but you should get the fundamental idea. Compile and run using the specified versions using Valgrind with --leak-check=full. If you comment Line 11 you will notice the problem can no longer be produced. Adding pollitems with zloop_poller appears to make the problem worse, but I haven't an example ready to prove it beyond reasonable doubt.
The text was updated successfully, but these errors were encountered:
I found some resources about "leaks" related with pthread_create, which is what ztread_new uses underneath. This controversy is more related with pthread_create than with czmq so I'm closing this.
Summary: When utilizing a zloop from within a thread spawned by zthread valgrind claims that some blocks are possibly lost and some are still reachable. The problem only occurs if you start the zloop.
Details:
OS: Debian 6.0.7
Compiler: gcc (Debian 4.4.5-8) 4.4.5
Valgrind: valgrind-3.6.0.SVN-Debian
Notes: The example isn't exactly the most sensible thing but you should get the fundamental idea. Compile and run using the specified versions using Valgrind with --leak-check=full. If you comment Line 11 you will notice the problem can no longer be produced. Adding pollitems with zloop_poller appears to make the problem worse, but I haven't an example ready to prove it beyond reasonable doubt.
The text was updated successfully, but these errors were encountered: