5. Regressions¶
If you’re upgrading to 6.1.0, then only 6.1.0 Regressions apply to you:
- 5.1. Regressions in 6.1.0
- 5.1.1. Core Libraries
- 5.1.1.1. XSD Issue: order enforced in <publisher> tag
- 5.1.1.2. Memory leak modifying flow_controller_name or filter_name QoS programmatically with DDS_String_dup
- 5.1.1.3. Samples lost if multiple readers were created in same locator and push_on_write was set to false
- 5.1.1.4. XML parser crashed from infinite recursion when XML QoS configuration contained inheritance loop
- 5.1.1.5. Invalid serialization of samples with types containing nested structures with primitive members that require padding
- 5.1.1.6. Significant performance degradation when using MultiChannel DataWriters
- 5.1.2. RTI Code Generator
- 5.1.3. RTI TLS Support
- 5.1.4. RTI Security Plugins
- 5.1.5. RTI Routing Service
- 5.1.1. Core Libraries
If you’re upgrading to 6.0.1, then only 6.0.1 Regressions apply to you:
- 5.2. Regressions in 6.0.1
- 5.2.1. Core Libraries
- 5.2.1.1. XSD Issue: order enforced in <publisher> tag
- 5.2.1.2. Memory leak modifying flow_controller_name or filter_name QoS programmatically with DDS_String_dup
- 5.2.1.3. Samples lost if multiple readers were created in same locator and push_on_write was set to false
- 5.2.1.4. XML parser crashed from infinite recursion when XML QoS configuration contained inheritance loop
- 5.2.1.5. Fixed in 6.1.0
- 5.2.2. RTI Code Generator
- 5.2.3. RTI Routing Service
- 5.2.4. RTI Recording Service
- 5.2.5. RTI Prototyper
- 5.2.1. Core Libraries
If you’re upgrading to 6.0.0 only, then 6.0.0 Regressions apply to you:
- 5.3. Regressions in 6.0.0
- 5.3.1. RTI Connext DDS Core Libraries
- 5.3.1.1. XSD issue: order enforced in <publisher> tag
- 5.3.1.2. Memory leak modifying flow_controller_name or filter_name QoS programmatically with DDS_String_dup
- 5.3.1.3. Fixed in 6.1.0
- 5.3.1.4. Fixed in 6.0.1
- 5.3.1.4.1. XSD issues
- 5.3.1.4.2. Dynamic Data issues
- 5.3.1.4.2.1. Segmentation fault when using unkeyed DynamicData DataReader with content filter and writer-side filtering
- 5.3.1.4.2.2. Invalid serialization of samples with types containing primitive members that require padding
- 5.3.1.4.2.3. Possible data corruption or crash when using DynamicData and a type with inheritance
- 5.3.1.4.2.4. Missing parameter checking for several DynamicData APIs results in segmentation faults or incorrect return codes
- 5.3.1.4.2.5. Binding to unset optional member causes some operations on parent DynamicData object to fail
- 5.3.1.4.3. Discovery does not complete, and there is no error
- 5.3.1.4.4. Crash when deserialized_type_object_dynamic_allocation_threshold set to 0
- 5.3.1.4.5. Wrong return code for DDS::DataWriter::get_matched_subscription_data and DDS::DataReader::get_matched_publication_data
- 5.3.1.4.6. DataReader reports incorrect sample lost and rejected when receiving coherent set
- 5.3.1.4.7. QoS policies not resolved to correct values
- 5.3.2. RTI Security Plugins
- 5.3.2.1. Fixed in 6.0.1
- 5.3.2.1.1. Possible lack of SUBSCRIPTION_MATCHED_STATUS if a DataWriter loses liveliness with the DataReader
- 5.3.2.1.2. Applications directly calling OpenSSL APIs after DomainParticipant deletion may crash
- 5.3.2.1.3. DataWriter does not report PUBLICATION_MATCHED_STATUS for DataReaders that are inactive when it receives their key material
- 5.3.2.1. Fixed in 6.0.1
- 5.3.3. RTI Code Generator
- 5.3.3.1. Change in behavior in C and traditional C++ for sequences of bounded strings under certain conditions when code is generated with optimization level 1 or 2
- 5.3.3.2. Fixed in 6.0.1
- 5.3.3.2.1. Invalid serialization of samples with types containing primitive members that require padding
- 5.3.3.2.2. Java exception during serialization/deserialization of keyed types whose key is an unkeyed nested type with unbounded members
- 5.3.3.2.3. Incorrect deserialization in .Net of samples from certain types when published from a writer with disable_inline_keyhash set to true
- 5.3.3.2.4. Generated code in traditional C++ with namespaces for an IDL containing a nested module called “rti” will not compile
- 5.3.4. RTI Routing Service
- 5.3.5. RTI Recording Service
- 5.3.6. RTI Cloud Discovery Service
- 5.3.1. RTI Connext DDS Core Libraries