zbentley commented on issue #6463:
URL: https://github.com/apache/pulsar/issues/6463#issuecomment-910747646
Though I guess that raises a larger question: for consumers of the C++ API,
it might be desirable in some cases to provide a producer object without
providing the ability to create a
zbentley commented on issue #6463:
URL: https://github.com/apache/pulsar/issues/6463#issuecomment-910743817
@merlimat I suggest solving it in Python: have producer objects, when
created, store a Python-side reference to the Client that created them.
Python's cyclic garbage collector should
zbentley commented on issue #6463:
URL: https://github.com/apache/pulsar/issues/6463#issuecomment-909587000
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe,
zbentley commented on issue #6463:
URL: https://github.com/apache/pulsar/issues/6463#issuecomment-909609025
@BewareMyPower I suggest updating this issue's description to reflect
affected platforms, e.g. `Pulsar client segfaults Python if any Producer
instance outlives the garbage collectio
zbentley commented on issue #6463:
URL: https://github.com/apache/pulsar/issues/6463#issuecomment-909587000
I am also affected by this (pulsar client `2.8.0.post0`, broker 2.8.0
standalone, Python 3.9.6 on MacOS 10.11). The following script reliably
reproduces the segfault:
```
i
