Emanuele Sabellico

Thanks @tradercentric @KalleOlaviNiemitalo I've updated the issue so it corresponds to the fix.

Thanks for the report. In provided stack trace it's just the example that is leaking memory, because the topic isn't destroyed.

Found and fixed the memory leak that happens in these examples `rdkafka_example` and `rdkafka_example_cpp` [here](https://github.com/confluentinc/librdkafka/pull/4669). Happens since 2.0.2 when using `rd_kafka_consume_stop` on a partition unknown to the client, for example...

This seems related https://github.com/confluentinc/librdkafka/issues/4362

The signal mask is set to block all signals. A new thread is created that inherits the signal mask blocking all signals. Then the original signal mask is restored. This...

It restores the original signmask, not the one with all blocked signal, check these lines https://github.com/confluentinc/librdkafka/blob/62165e6d09082454138948922b96b54bd55058a8/rdkafka.c#L922 https://github.com/confluentinc/librdkafka/blob/62165e6d09082454138948922b96b54bd55058a8/rdkafka.c#L950 The race condition Magnus was referring to happens if the signal handler is...

> And while creating it also blocks signals but then restore it to all-blocked, since they had been blocked already above: No, they are restored to `oldset`, that is the...

@felixschlegel Thanks for your PR. Are you sure this is the only change that's required? I've tried compiling and linking with BoringSSL and there are these different things: ``` rdkafka_cert.c:...

are you able to compile after configuring librdkafka 2.3.0 with `./configure --enable-werror` ? Because those are marked as warnings but are important (RAND_priv_bytes is missing for example)

To clarify this PR doesn't give support for BoringSSL, it still needs these defines that are in your `swift-kafka-client`. We're open to receive a patch for complete, even if unofficial,...