Full shared memory files cleanup after application crash

[eketh]

Hello,
we are using FastDDS as an IPC framework in our application running on an embedded Linux system, having both UDP and shared memory transport options enabled. What we observed is a similar problem to the one described previously in issue #2790, namely there are still fastrtps files remaining in /dev/shm after a program runtime error. Even after an execution of the fastdds shm clean script, there is a couple of fastrtps_portXXXX and sem.fastrtps_portXXXX_mutex files remaining in the shared memory directory.
As the environment where we run our application is very resource-constrained, we would like to reduce the amount of files remaining in memory after application crash. Therefore, we have a couple of questions to help us implement a proper recovery cleanup procedure on our end:

1. Can these fastrtps_port and sem.fastrtps_port files that are left in /dev/shm after an application crash and fastdds shm clean execution be safely removed?
2. Can these files remaining in memory after a previous crash affect publishers/subscribers runtime behavior in any way? If not, are they just overwritten/reused by the new runtime?