5.17. Instances

5.17.1. [Critical] Two log messages used memory after it was freed *

When the instance state consistency feature was enabled and the logging level was set to local, two log messages could have been generated that used memory after the memory had been freed.

[RTI Issue ID CORE-14475]

5.17.2. [Major] Instance state consistency may not have worked for DataReaders using multiple data representations *

Instance state consistency updates may not have been applied for DataReaders using multiple data representations. Note that the state of the instance would only have been incorrect if the DataReader was using a Durability of VOLATILE and the instance of interest had not changed state during the disconnection.

[RTI Issue ID CORE-14076]

5.17.3. [Major] Indeterminate instance state in systems with multiple DataWriters *

Instance state consistency is used to ensure that, upon recovering from a disconnection, DataReaders have the latest instance state data for each instance. In scenarios where a DataReader lost liveliness with multiple DataWriters, there may have been some indeterminism in the final state, depending on which DataWriter the DataReader recovered liveliness with first. This issue has been resolved for DataReaders that have a DestionationOrderKind of BY_SOURCE_TIMESTAMP. Upon recovering liveliness, the eventual state of each instance will be the latest state across all DataWriters with which liveliness has been recovered.

[RTI Issue ID CORE-13740]

* This bug does not affect you if you are upgrading from 6.1.x or earlier.