Open trevorr opened 1 week ago
Thank you for the report. I can't reproduce it, but looking at valgrind and the stacktrace, I think it's the same one as #34 . As far as I understand, it's because we're sending the message from the consume loop thread, to the event loop thread, but by the time it makes to the event loop thread, the callback it's supposed to call is destroyed already.
It seems to be specific to the consume() loop in the non-promisified API.
I'll keep both around until I'm certain that they are the same.
Environment Information
Steps to Reproduce
Here's the stack trace:
(This even occurs with a fix for #161.)