When can I free memory of data structures passed to RTI Connext?

Note: Applies to RTI Connext versions 4.x and above

Configuration data structures such as QoS structures are passed to RTI Connext by value, as they are only used to initialize the internal state of the entity being created. After the call to create the object, the user application can free the memory. This is not true of listeners, which may not be deleted until the entity they are attached to has been deleted. 

A slightly more complex case involves the properties of the default transports. There are several interface lists referenced by these structures. For example, the  allow_interfaces_list can be used to restrict RTI Connext to a subset of network interfaces on a multi-homed host. These user-managed data structures referenced by the transport property are used during transport initialization, which occurs when the DomainParticipant is enabled. After enabling the participant, you can safely dispose of the memory.