10.4.16. Memory Leaks/Growth¶
10.4.16.1. [Major] Possible memory leaks in CDR_WstringSeq_set_maximum¶
If any of the buffers’ allocation failed for a CDR_Wstring sequence,
the previously allocated buffers would not be freed, causing a memory
leak.
[RTI Issue ID MICRO-10036]
10.4.16.2. [Major] Possible memory leaks in CDR_WstringSeq_copy¶
If any of the buffers’ allocation failed for a CDR_Wstring sequence,
the previously allocated buffers would not be freed, causing a memory
leak.
[RTI Issue ID MICRO-9969]
10.4.16.3. [Major] DDS_DomainParticipantFactory_get_instance() not memory safe on some architectures¶
On architectures with weak memory ordering (such as ARM),
DDS_DomainParticipantFactory_get_instance() was not guaranteed to be
memory safe.
[RTI Issue ID MICRO-8004]
10.4.16.4. [Major] Possible memory leak from failed write of a new instance¶
Resources may have been leaked if the value of max_samples was
greater than (max_instances * max_samples_per_instance) and the
DataWriter’s sample resources had been exhausted.
[RTI Issue ID MICRO-3129]
10.4.16.5. [Minor] Possible memory leak when finalizing Publishers or Subscribers with Partition QoS¶
Under specific conditions, Publishers and Subscribers that had user-defined Partition QoS policies would leak memory when finalized.
[RTI Issue ID MICRO-11336]
10.4.16.6. [Minor] Possible memory leak when Entities experienced errors on topic creation¶
During DomainParticipant topic creation, Entities would occasionally leak topic data memory if topic creation encountered an error.
[RTI Issue ID MICRO-11341]