Matt-Esch commented on issue #191: URL: https://github.com/apache/pulsar-client-node/issues/191#issuecomment-1025051892
This is caused by a race condition. Currently nothing prevents you from closing the client with pending async operations in flight. Closing the client ends up killing all of the boost::asio executors. This means we see async workers like ProducerNewInstanceWorker calling into pulsar_client_create_producer on a client that has either already been closed or is about to be closed. By the time it gets to invoking a certain async function, the state of the executor is invalid because it has been closed prematurely. We have to avoid invoking methods that create resources from a closed client. -- 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, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
