BewareMyPower commented on issue #14665:
URL: https://github.com/apache/pulsar/issues/14665#issuecomment-1076107035


   It can be reproduced easily in local env as well.
   
   ```
   Process 10340 stopped
     thread #1: tid = 0x2ab53, 0x0000000104907602 
libpulsar.2.10.0-SNAPSHOT.dylib`std::__1::__tree<std::__1::__value_type<std::__1::basic_string<char,
 std::__1::char_traits<char>, std::__1::allocator<char> >, 
std::__1::weak_ptr<pulsar::ClientConnection> >, 
std::__1::__map_value_compare<std::__1::basic_string<char, 
std::__1::char_traits<char>, std::__1::allocator<char> >, 
std::__1::__value_type<std::__1::basic_string<char, 
std::__1::char_traits<char>, std::__1::allocator<char> >, 
std::__1::weak_ptr<pulsar::ClientConnection> >, 
std::__1::less<std::__1::basic_string<char, std::__1::char_traits<char>, 
std::__1::allocator<char> > >, true>, 
std::__1::allocator<std::__1::__value_type<std::__1::basic_string<char, 
std::__1::char_traits<char>, std::__1::allocator<char> >, 
std::__1::weak_ptr<pulsar::ClientConnection> > > 
>::destroy(std::__1::__tree_node<std::__1::__value_type<std::__1::basic_string<char,
 std::__1::char_traits<char>, std::__1::allocator<char> >, 
std::__1::weak_ptr<pulsar::Client
 Connection> >, void*>*), queue = 'com.apple.main-thread'
   * thread #2: tid = 0x2ab6e, 0x000000010474ce7f 
libpulsar.2.10.0-SNAPSHOT.dylib`bool 
std::__1::__cxx_atomic_compare_exchange_strong<pulsar::PeriodicTask::State>(__a=0x0000000000000010,
 __expected=0x000070000b3b21a7, __value=Closing, 
__success=memory_order_seq_cst, __failure=memory_order_seq_cst) at 
atomic:1039:12, stop reason = EXC_BAD_ACCESS (code=1, address=0x10)
     thread #3: tid = 0x2ab6f, 0x00007ff81916b506 
libsystem_kernel.dylib`__psynch_cvwait + 10
   ```
   
   It looks like to be a bug of C++ 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to