4.11. APIs (Java)

4.11.1. Possible memory leak in DynamicData copy constructor

In the Java API only, under certain conditions, copying a DynamicData object using the constructor that receives another DynamicData object may have leaked native heap memory. This problem has been fixed.

[RTI Issue ID CORE-13609]

4.11.2. Some ReliabilityQos methods did not consider the instance state consistency QoS

The copy_from and equals methods, as well as the implementation of the hash code for objects of that class, were not complete; they were missing the instance_state_consistency_kind QoS. This problem has been remedied.

[RTI Issue ID CORE-13785]