Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DataSharing/ReaderPool.hpp error #5267

Open
1 task done
kaola-zero opened this issue Sep 26, 2024 · 0 comments
Open
1 task done

DataSharing/ReaderPool.hpp error #5267

kaola-zero opened this issue Sep 26, 2024 · 0 comments
Labels
triage Issue pending classification

Comments

@kaola-zero
Copy link

Is there an already existing issue for this?

  • I have searched the existing issues

Expected behavior

The node not dead.

Current behavior

lQLPJwkbyvjBQK_NAmbNBtWw3_fMXsITCC0G3QkN5eRyAA_1749_614
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);
pubsub_participant_ = factory->create_participant(participant_id_, 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 kaola-zero added the triage Issue pending classification label Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Issue pending classification
Projects
None yet
Development

No branches or pull requests

1 participant