Exit problem with cv.wait()

[RookieCLY]

Is there an already existing issue for this?

• I have searched the existing issues

Expected behavior

Successfully exited

Current behavior

The process of the example Helloworld cannot exit normally because a thread cannot exit normally.
The following is stack information for threads that cannot exit normally：
0x0000000000000000
ntdll.dll!NtWaitForMultipleObjects+0x14
KERNELBASE.dll!WaitForMultipleObjectsEx+0xf0
KERNELBASE.dll!WaitForMultipleObjects+0xe
libwinpthread-1.dll!pthread_rel_time_in_ms+0x1b6
libwinpthread-1.dll!pthread_cond_init+0x1e9
libwinpthread-1.dll!pthread_cond_init+0x51b
libwinpthread-1.dll!pthread_cond_destroy+0x56
libstdc++-6.dll!ZNSt18condition_variableD2Ev+0x9
libfastdds.dll!ZNK8eprosima7fastdds4rtps8Endpoint7getGuidEv+0x80f1
libfastdds.dll!ZNK8eprosima7fastdds4rtps8Endpoint7getGuidEv+0x8521
ucrtbase.dll!execute_onexit_table+0x156
ucrtbase.dll!execute_onexit_table+0x7b
ucrtbase.dll!execute_onexit_table+0x34
libfastdds.dll+0x1092
libfastdds.dll+0x1219
ntdll.dll!RtlActivateActivationContextUnsafeFast+0x11d
ntdll.dll!LdrShutdownProcess+0x22a
ntdll.dll!RtlExitUserProcess+0xad
KERNEL32.DLL!FatalExit+0xb
msvcrt.dll!exit+0x85
msvcrt.dll!initterm_e+0x245
MBus.exe+0x14a5
MBus.exe+0x14e6
KERNEL32.DLL!BaseThreadInitThunk+0x14
ntdll.dll!RtlUserThreadStart+0x21

I want to know what part of the code is thread blocking/waiting. Is it in RTPSParticipantImpl::disable()? I'm not sure, so I hope to get your help.

Steps to reproduce

Program：HelloWorld example with a while loop in main(). While the loop is break, the process should exit but not.
MinGW-lib: FastDDS compiled by MinGW14.2, can be find in here

Fast DDS version/commit

FastDDS v3.1.0
Windows
MinGW 14.2

Platform/Architecture

Other. Please specify in Additional context section.

Transport layer

Intra-process

Additional context

No response

XML configuration file

Relevant log output

Network traffic capture

No response

[Carlosespicur]

Hi @RookieCLY,
Currently MinGW is not officially supported. If you manage to solve the problem, please feel free to open a PR.
For further help, please contact us directly to [email protected] for further work on this issue if this is a need for your project.