3 ms·
that is/was a problem with zeroMQ, not gperftools: 27 SIGPROF terminate process profiling timer alarm (see setitimer(2)) its use is specifically
by vectorEQ 7y ago
that is/was a problem with zeroMQ, not gperftools:
27 SIGPROF terminate process profiling timer alarm (see setitimer(2))
its use is specifically what that signal is for.
Additionally, it seems fixed in zeroMQ for some things already in 2016... so i doubt thats still valid issue.