9.4. Regressions in 6.0 LTS
The following regressions were introduced in Connext 6.0 LTS, which is a culmination of releases 6.0.0 and 6.0.1.
- 9.4.1. Introduced in 6.0.0
- 9.4.1.1. Core Libraries
- 9.4.1.1.1. Unexpected precondition error sending repair to DataReaders with 16 locators
- 9.4.1.1.2. Non-Java register_type fails if the maximum size is greater than 2 GB
- 9.4.1.1.3. XCDR serialization of a mutable union with an unknown discriminator value is not compliant with OMG specification
- 9.4.1.1.4. Participant may receive RTPS traffic over SHMEM transport not intended for participant
- 9.4.1.1.5. Instance handling on a DataReader and filtering operations in ContentFilteredTopics, QueryConditions, TopicQueries, and Multi-Channel DataWriters may fail
- 9.4.1.1.6. Creating DynamicDataTypePlugin with TypeCode from discovery and using content filtering causes segmentation fault
- 9.4.1.1.7. Crash with NULL listeners and non-none status masks in C applications that mix types with and without Zero Copy
- 9.4.1.1.8. Application using Monitoring Libraries produces segmentation fault during DataReader creation
- 9.4.1.1.9. Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator
- 9.4.1.1.10. Unbounded memory growth in Spy when discovering multiple endpoints with the same Topics and types
- 9.4.1.1.11. Types Containing Typedefs sent without the typedefs in discovery when using DynamicData
- 9.4.1.1.12. XSD issue: order enforced in <publisher> tag
- 9.4.1.1.13. Invalid key deserialization for mutable derived types with key members
- 9.4.1.1.14. Malformed samples with invalid strings not dropped by DataReader in C, traditional C++, and modern C++
- 9.4.1.1.15. VxWorks kernel mode shared memory doesn’t work after restarting an application
- 9.4.1.1.16. Serialization of string members does not check for null-terminated strings in C, traditional C++, and modern C++
- 9.4.1.1.17. Discovery issues when reusing shared memory segments
- 9.4.1.1.18. Unexpected log message when calling DataWriter::get_matched_subscription_data or DataReader::get_matched_publication_data on unmatched endpoints
- 9.4.1.1.19. XSD issues
- 9.4.1.1.20. Dynamic Data issues
- 9.4.1.1.20.1. Segmentation fault when using unkeyed DynamicData DataReader with content filter and writer-side filtering
- 9.4.1.1.20.2. Invalid serialization of samples with types containing primitive members that require padding
- 9.4.1.1.20.3. Possible data corruption or crash when using DynamicData and a type with inheritance
- 9.4.1.1.20.4. Missing parameter checking for several DynamicData APIs results in segmentation faults or incorrect return codes
- 9.4.1.1.20.5. Binding to unset optional member causes some operations on parent DynamicData object to fail
- 9.4.1.1.21. Discovery does not complete, and there is no error
- 9.4.1.1.22. Crash when deserialized_type_object_dynamic_allocation_threshold set to 0
- 9.4.1.1.23. Wrong return code for DDS::DataWriter::get_matched_subscription_data and DDS::DataReader::get_matched_publication_data
- 9.4.1.1.24. DataReader reports incorrect sample lost and rejected when receiving coherent set
- 9.4.1.1.25. QoS policies not resolved to correct values
- 9.4.1.2. Security Plugins
- 9.4.1.2.1. Discovery time scales poorly
- 9.4.1.2.2. Possible lack of SUBSCRIPTION_MATCHED_STATUS if a DataWriter loses liveliness with the DataReader
- 9.4.1.2.3. Applications directly calling OpenSSL APIs after DomainParticipant deletion may crash
- 9.4.1.2.4. DataWriter does not report PUBLICATION_MATCHED_STATUS for DataReaders that are inactive when it receives their key material
- 9.4.1.3. Code Generator
- 9.4.1.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
- 9.4.1.3.2. -d64 flag missing in generated Java makefile for Red Hat Enterprise Linux 8.0
- 9.4.1.3.3. Invalid key deserialization for mutable derived types with key members
- 9.4.1.3.4. Malformed samples with invalid strings not dropped by DataReader in C, traditional C++, and modern C++
- 9.4.1.3.5. Invalid serialization of samples with types containing primitive members that require padding
- 9.4.1.3.6. Java exception during serialization/deserialization of keyed types whose key is an unkeyed nested type with unbounded members
- 9.4.1.3.7. Incorrect deserialization in .Net of samples from certain types when published from a writer with disable_inline_keyhash set to true
- 9.4.1.3.8. Generated code in traditional C++ with namespaces for an IDL containing a nested module called “rti” will not compile
- 9.4.1.4. Persistence Service
- 9.4.1.5. Routing Service
- 9.4.1.5.1. Vulnerability: Potential stack corruption in Routing Service when using malicious XML configuration document
- 9.4.1.5.2. Unbounded memory growth when restarting Service or creating/deleting DomainRoutes
- 9.4.1.5.3. Large per-sample memory usage in Routing Service
- 9.4.1.5.4. Routing Service remote shell: Adding to initial peers list does not work, possible segmentation fault
- 9.4.1.5.5. Incorrect content filtering and “RTICdrTypeCodeUtils_type_has_external_members:!get member” error
- 9.4.1.5.6. Create method in Service API fails to parse XML snippets that start with ‘str://’
- 9.4.1.5.7. Memory leak if malformed configuration file prevents Routing Service creation
- 9.4.1.5.8. Executable ignores logging QoS
- 9.4.1.6. Recording Service
- 9.4.1.6.1. Segmentation fault after discovering application that uses UserData QoS Policy
- 9.4.1.6.2. Executable does not log build ID for DDS libraries
- 9.4.1.6.3. Legacy deserialized database table cannot be replayed or converted if it contains compact byte sequences or arrays
- 9.4.1.6.4. Segmentation fault in Replay Service or Converter if recorded topics have “::” in their names
- 9.4.1.7. Cloud Discovery Service
- 9.4.1.8. Queuing Service
- 9.4.1.1. Core Libraries
- 9.4.2. Introduced in 6.0.1
- 9.4.2.1. Core Libraries
- 9.4.2.1.1. Samples lost if multiple readers created in same locator and push_on_write is set to false
- 9.4.2.1.2. XML parser crashes from infinite recursion when XML QoS configuration contains inheritance loop
- 9.4.2.1.3. Possible issues with communication and enabling DomainParticipant on Windows systems if network interface has multiple IP addresses
- 9.4.2.1.4. Failure to allocate memory larger than 2 GB
- 9.4.2.2. Routing Service
- 9.4.2.3. Recording Service
- 9.4.2.4. Prototyper
- 9.4.2.5. Security Plugins
- 9.4.2.1. Core Libraries