5.2.20. Memory Leaks/Growth

5.2.20.1. [Critical] Spike in memory usage when creating a DataWriter using Durable Writer History to restore samples

When creating a DataWriter that used Durable Writer History to restore a large number of samples, the memory usage incorrectly grew to a large amount and then shrunk back down. This problem has been fixed by reducing the memory usage.

[RTI Issue ID CORE-15802]

5.2.20.2. [Major] RTI DDS Spy showed DDS_DataReader_get_matched_publication_participant_data error before leaking memory

When discovering the deletion of a DataWriter or DataReader immediately after discovering the deletion of the DomainParticipant associated with the DataWriter or DataReader, DDS Spy incorrectly generated these errors before leaking memory:

DDS_DataReader_get_matched_publication_participant_data:ERROR: Failed to get discovered_participant_data
get_matched_publication_participant_data error 4
ERROR DDS_SampleInfoSeq_set_maximum:failed to assert buffer must not be loaned

This problem only affected versions 7.3.0 and above.

[RTI Issue ID CORE-15629]

5.2.20.3. [Major] DomainParticipantFactory finalization failed even if all the DomainParticipants were deleted

When creating or deleting DomainParticipants concurrently from different threads, the finalization of the DomainParticipantFactory could fail, stating that “Not all the participants created were destroyed” even after deleting all the DomainParticipants.

[RTI Issue ID CORE-14609]

5.2.20.4. [Minor] Memory leak upon Transport TCP creation failure because of invalid configuration

A failure during Transport TCP creation may have triggered a memory leak. The leak triggered when providing an invalid PropertyQos configuration to the transport.

[RTI Issue ID COREPLG-755]