sgf201

> @sgf201 I don't understand why you are pinging various people who aren't involved in this (nor why you didn't simply reopen #1097 after GitHub closed it automatically because I...

> @sgf201 try this: [eboasson@eff7e82](https://github.com/eboasson/cyclonedds/commit/eff7e8208ea5c02dda72f206e5561748961b8334) If you call this new `dds_ruthless_reset_for_child_after_fork` function in the child after forking, it resets everything by just `memset`ting things. It worked for a simple experiment...

 after apply this: [eboasson@eff7e82](https://github.com/eboasson/cyclonedds/commit/eff7e8208ea5c02dda72f206e5561748961b8334) , the father process and child process raise the same err,but it seems not fatal. some data lost which from another host.

@eboasson Recently, the environment in which dds is used has become more complex, and the pressure has increased. A strange problem has arisen. I think the time is when the...

> thanks ,It works when I set the reader "dds_qset_latency_budget(qos,DDS_SECS(0.1));"also. and I am curious about: 1.why the reader in same host can get msg which is not set the latency_buget...

> Did you make them reliable and set the "durability" QoS setting to "transient local" on both the reader and the writer? > > (If you want the writer to...

rmw_cyclonedds_cpp needs a deep refact to solve the allocator problem if making a custom destructor for the shared_ptr https://github.com/eclipse-iceoryx/iceoryx/issues/2159

@wjwwood I agree with your point, this issue should indeed be handled at the RMW layer. I'm not very familiar with the other RMW implementations, but in rmw_cyclonedds_cpp, they have...