win11 can not replay

[fatfly001]

Environment: Windows 11
Issue:

1. C:\record-replayer-install\bin\ddsreplayer.exe --log-verbosity "warning" -i C:\Users\xxxxx\Downloads\output_2023-07-24_08-38-53.mcap return directly without pub any message.
2. "[RTPS_TRANSPORT_SHM Error] Failed init_port fastrtps_port7415 " sometime will prompt this message.

Version:
C:\record-replayer-install\bin\ddsreplayer.exe -v
DDS Record & Replay v0.2.0
commit hash: 66492d1

Compile ENV:
C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Visual Studio 2019\Visual Studio Tools\VC\x64 Native Tools Command Prompt for VS 2019

Cmake:
C:\Users\xxxxxxxx>cmake --version
cmake version 3.24.1
CMake suite maintained and supported by Kitware (kitware.com/cmake).

wget https://raw.githubusercontent.com/eProsima/DDS-Record-Replay/main/ddsrecordreplay.repos ddsrecordreplay.repos

controller & ddsrecorder.exe seems good but ddsreplayer.exe which need help.

[juanlofer-eprosima]

Hi @RyanPangZheng

Was the file being replayed generated with the same DDS-Record-Replay version (commit)? There have been a couple of changes introduced that might affect backwards compatibility.

Also, could you please retest with the latest version available? We recently spotted a bug in mcap library that might have something to do with your issue.

Regarding your points:

1. Before digging any further, please make sure the MCAP file actually contains any messages. If empty, then this behaviour is to be expected. You can use mcap CLI to inspect the file, and/or visualize it with Foxglove Studio.

2. These are warnings related to Shared Memory Transport. When an application using this transport protocol is not properly closed, some allocated resources are not released and can interfere with posterior executions. This might be your case, please check the content of eprosima\\fastrtps_interprocess folder present somewhere in your system, and verify it is empty when no application using Fast-DDS (e.g. DDS-Record-Replay) is being run. If there are zombie resources, feel free to manually delete them, or use Fast-DDS CLI to achieve the same (fastdds shm clean).

Best regards