DataSharing/ReaderPool.hpp error

[kaola-zero]

Is there an already existing issue for this?

• [X] I have searched the existing issues

Expected behavior

The node not dead.

Current behavior

communication:/home/kaola/new_fastdds_ws/src/Fast-DDs-2.14.0/src/cpp/rtps/DataSharing/ReaderPool.hpp:68:virtualbooleprosima::fastrtps::rtps::ReaderPool::get_payload(eprosima::fastrtps::rtps::SerializedPayload_t&,eprosma::fastrtps::rtps::IPayloadPool&, prosima::fastrtps::rtps::CacheChange_t&):Assertionnullptr != dynamic_cast<DataSharingPayloadPool>(data_o wner)' failed.

Steps to reproduce

When I run fastdds2.14.0 it happened System environment : Arm Linux My Qos set: DomainParticipantQos pqos = PARTICIPANT_QOS_DEFAULT; pqos.name("Participant_pub"); auto factory = DomainParticipantFactory::get_instance(); factory->load_profiles(); factory->get_default_participant_qos(pqos); pqos.transport().use_builtin_transports = false; auto udp_transport = std::make_sharedeprosima::fastdds::rtps::UDPv4TransportDescriptor(); eprosima::fastrtps::rtps::Locator_t locator; eprosima::fastrtps::rtps::IPLocator::setIPv4(locator, 127, 0, 0, 1); locator.port = 22222; pqos.wire_protocol().default_multicast_locator_list.push_back(locator); pqos.transport().user_transports.push_back(udp_transport); pubsubparticipant = factory->create_participant(participantid, pqos);

Fast DDS version/commit

I user the version is 2.14.0

Platform/Architecture

Ubuntu Focal 20.04 arm64

Transport layer

UDPv4

Additional context

No response

XML configuration file

No response

Relevant log output

No response

Network traffic capture

No response

[kaola-zero]

More infomation: This error happened when I use "User-traffic Multicast Locators" configuration. And I use three device in one Network segment. When I only use one device. Error not happen. That "User-traffic Multicast Locators" division of groups is what?

[JesusPoderoso]

Hi @kaola-zero, thanks for using Fast DDS. Can you provide a reproducer?

[Mario-DL]

According to our CONTRIBUTING.md guidelines, I am closing this issue due to inactivity. Please, feel free to reopen it if necessary.