Application using fast-dds consumes high CPU when system time is updated in QNX

[GeekKrish]

Is there an already existing issue for this?

• I have searched the existing issues

Expected behavior

Updating/changing system time should not impact fast-dds functionality.

Current behavior

I have a qnx application using fast-dds 2.8,1. When system time is updated during application (dds) initialisation, the application starts consuming high cpu and assume fast-dds is some deadlock and dds initialisation does not

Steps to reproduce

1. Start custom dds test applocation .
2. immediately change system time

Fast DDS version/commit

2.8.1

Platform/Architecture

Other. Please specify in Additional context section.

Transport layer

Shared Memory Transport (SHM)

Additional context

No response

XML configuration file

Relevant log output

Network traffic capture

No response

[Mario-DL]

Hi @GeekKrish,
According to out RELEASE_SUPPORT, 2.8.x is not a currently supported version, so I am moving this issue to the proper discussion forum. Also, QNX is a tier 3 platform PLATFORM_SUPPORT

Bear in mind that the DDS standard just require DDS applications to have enough synchronized clocks. User should be very cautious with time jumps in this sense. Anyways, please double check if the issue persists using any of the 2.x supported versions either v2.10.6 or v2.14.4.

Also, please feel free for reaching our Commercial Support at [email protected] if you need support for your project

[GeekKrish]

Hi @Mario-DL,

Thanks for the quick feedback

I will evaluate with the versions suggested and come back on this. It might take a while as I need to compile these versions for qnx and also there is bunch of applications in the pipeline using dds for ipc.

Regards,
Shrisha