Incorrect memory access in the Output Traffic Manager in case of a UDP transport init error

[i-and]

Is there an already existing issue for this?

• [X] I have searched the existing issues

Expected behavior

Memory accesses are correct

Current behavior

Memory accesses are not correct

Steps to reproduce

The error occurs if an exception occurs inside the try { ...} catch (asio::system_error const&e) block in the method bool UDPTransportInterface::OpenOutputChannel(SendResourceList& sender_resource_list, const Locator& locator)

Fast DDS version/commit

master

Platform/Architecture

Ubuntu Focal 20.04 amd64

Transport layer

UDPv4

Additional context

There is not enough early exit from the method OutputTrafficManager::set_statistics_message_data() in case it == collection_.end(). The existing assert(it != collection_.and()) not enough, as it is disabled in the Release configuration.

XML configuration file

No response

Relevant log output

No response

Network traffic capture

No response

[Mario-DL]

Hi @i-and, Thanks for using Fast DDS and for the report. We would need more additional information on the scenario. Could you provide some reproducer ?

[JesusPoderoso]

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