7. Regressions

Regressions are documented in the release in which they were introduced, as well as the releases to which they still apply. For example, a regression introduced in 6.0.0 and not fixed until 6.1.0 will be listed in both the 6.0.0 and 6.0.1 sections below.

Note

Use the links below to see the regressions that were either introduced in that release or still exist in that release.

7.0.0 Regressions
If you’re upgrading to 7.0.0, then only 7.0.0 Regressions apply to you:

• 7.1. Regressions in 7.0.0
  • 7.1.1. Core Libraries
    • 7.1.1.1. TCP transport debug library in Windows does not work with IOCP socket monitoring

6.1.1 Regressions
If you’re upgrading to 6.1.1, then only 6.1.1 Regressions apply to you:

• 7.2. Regressions in 6.1.1
  • 7.2.1. Core Libraries
    • 7.2.1.1. Fixed in 7.0.0
      • 7.2.1.1.1. Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator

6.1.0 Regressions
If you’re upgrading to 6.1.0, then only 6.1.0 Regressions apply to you:

• 7.3. Regressions in 6.1.0
  • 7.3.1. Core Libraries
    • 7.3.1.1. Fixed in 7.0.0
      • 7.3.1.1.1. Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator
    • 7.3.1.2. Fixed in 6.1.1
      • 7.3.1.2.1. Linking static Linux or QNX libraries with object files built with -fPIC will fail
      • 7.3.1.2.2. XSD Issue: order enforced in <publisher> tag
      • 7.3.1.2.3. Invalid key deserialization for mutable derived types with key members
      • 7.3.1.2.4. Malformed samples with invalid strings not dropped by DataReader in C, traditional C++, and modern C++
      • 7.3.1.2.5. Samples lost if multiple readers were created in same locator and push_on_write was set to false
      • 7.3.1.2.6. XML parser crashed from infinite recursion when XML QoS configuration contained inheritance loop
      • 7.3.1.2.7. Invalid serialization of samples with types containing nested structures with primitive members that require padding
      • 7.3.1.2.8. Possible segmentation fault when receiving samples containing wstrings
      • 7.3.1.2.9. Significant performance degradation when using MultiChannel DataWriters
      • 7.3.1.2.10. Significant performance regression on Windows when using OpenSSL 1.1.1 libraries in 6.1.0
      • 7.3.1.2.11. ReadCondition may incorrectly stay enabled after sample in READ sample state removed from the DataReader’s queue
      • 7.3.1.2.12. Missing SampleInfo.ReceptionTimestamp property (C# API only)
  • 7.3.2. RTI Code Generator
    • 7.3.2.1. Fixed in 6.1.1
      • 7.3.2.1.1. Change in behavior in C and traditional C++ for bounded sequences under certain conditions
      • 7.3.2.1.2. Invalid key deserialization for mutable derived types with key members
      • 7.3.2.1.3. Malformed samples with invalid strings not dropped by DataReader in C, traditional C++, and modern C++
      • 7.3.2.1.4. Invalid serialization of samples with types containing nested structures with primitive members that require padding
  • 7.3.3. RTI Admin Console
    • 7.3.3.1. Fixed in 6.1.1
      • 7.3.3.1.1. High CPU usage by Admin Console
  • 7.3.4. RTI TLS Support
    • 7.3.4.1. Fixed in 6.1.1
      • 7.3.4.1.1. hello_world_tcp example root and intermediate CAs expire too early
      • 7.3.4.1.2. Significant performance regression on Windows when using OpenSSL 1.1.1 libraries in 6.1.0
  • 7.3.5. RTI Security Plugins
    • 7.3.5.1. Fixed in 6.1.1
      • 7.3.5.1.1. Significant performance regression on Windows when using OpenSSL 1.1.1 libraries in 6.1.0
      • 7.3.5.1.2. use_530_partitions incorrectly allowed any non-empty partitions
      • 7.3.5.1.3. Permissions document incorrectly disallowed unescaped special characters in a subject name
  • 7.3.6. RTI Routing Service
    • 7.3.6.1. Fixed in 6.1.1
      • 7.3.6.1.1. Unbounded memory growth when restarting Service or creating/deleting DomainRoutes
      • 7.3.6.1.2. Crash in Routing Service executable when providing the same -Dname=value pair twice

6.0.1 Regressions
If you’re upgrading to 6.0.1, then only 6.0.1 Regressions apply to you:

• 7.4. Regressions in 6.0.1
  • 7.4.1. Core Libraries
    • 7.4.1.1. Fixed in 7.0.0
      • 7.4.1.1.1. Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator
    • 7.4.1.2. Fixed in 6.1.1
      • 7.4.1.2.1. XSD Issue: order enforced in <publisher> tag
      • 7.4.1.2.2. Invalid key deserialization for mutable derived types with key members
      • 7.4.1.2.3. Malformed samples with invalid strings not dropped by DataReader in C, traditional C++, and modern C++
      • 7.4.1.2.4. Samples lost if multiple readers were created in same locator and push_on_write was set to false
      • 7.4.1.2.5. XML parser crashed from infinite recursion when XML QoS configuration contained inheritance loop
      • 7.4.1.2.6. Possible segmentation fault when receiving samples containing wstrings
    • 7.4.1.3. Fixed in 6.1.0
      • 7.4.1.3.1. Possible issues with communication and enabling DomainParticipant on Windows systems if network interface had multiple IP addresses
      • 7.4.1.3.2. Failure to allocate memory larger than 2 GB
  • 7.4.2. RTI Code Generator
    • 7.4.2.1. Fixed in 6.1.1
      • 7.4.2.1.1. Change in behavior in C and traditional C++ for bounded sequences under certain conditions
      • 7.4.2.1.2. Invalid key deserialization for mutable derived types with key members
      • 7.4.2.1.3. Malformed samples with invalid strings not dropped by DataReader in C, traditional C++, and modern C++
  • 7.4.3. RTI Routing Service
    • 7.4.3.1. Fixed in 6.1.1
      • 7.4.3.1.1. Unbounded memory growth when restarting Service or creating/deleting DomainRoutes
    • 7.4.3.2. Fixed in 6.1.0
      • 7.4.3.2.1. Create method in Service API fails to parse XML snippets that start with ‘str://’
  • 7.4.4. RTI Recording Service
    • 7.4.4.1. Fixed in 6.1.0
      • 7.4.4.1.1. Crash if monitoring enabled and TopicGroup matched with Topic name containing ‘/’ character
      • 7.4.4.1.2. Segmentation fault after discovering application that used UserData QoS Policy
  • 7.4.5. RTI Prototyper
    • 7.4.5.1. Fixed in 6.1.0
      • 7.4.5.1.1. Prototyper broken in 6.0.1

6.0.0 Regressions
If you’re upgrading to 6.0.0, then 6.0.0 Regressions apply to you:

• 7.5. Regressions in 6.0.0
  • 7.5.1. RTI Connext Core Libraries
    • 7.5.1.1. Fixed in 7.0.0
      • 7.5.1.1.1. Continuous creation of TopicQueries may lead to unnecessary memory fragmentation in OS memory allocator
    • 7.5.1.2. Fixed in 6.1.1
      • 7.5.1.2.1. XSD issue: order enforced in <publisher> tag
      • 7.5.1.2.2. Invalid key deserialization for mutable derived types with key members
      • 7.5.1.2.3. Malformed samples with invalid strings not dropped by DataReader in C, traditional C++, and modern C++
    • 7.5.1.3. Fixed in 6.1.0
      • 7.5.1.3.1. Unexpected log message when calling DataWriter::get_matched_subscription_data or DataReader::get_matched_publication_data on unmatched endpoints
    • 7.5.1.4. Fixed in 6.0.1
      • 7.5.1.4.1. XSD issues
        • 7.5.1.4.1.1. Order enforced in <domain_participant> tag
        • 7.5.1.4.1.2. XSD validation fails if topic_ref or register_type_ref uses some non-alphanumeric characters
      • 7.5.1.4.2. Dynamic Data issues
        • 7.5.1.4.2.1. Segmentation fault when using unkeyed DynamicData DataReader with content filter and writer-side filtering
        • 7.5.1.4.2.2. Invalid serialization of samples with types containing primitive members that require padding
        • 7.5.1.4.2.3. Possible data corruption or crash when using DynamicData and a type with inheritance
        • 7.5.1.4.2.4. Missing parameter checking for several DynamicData APIs results in segmentation faults or incorrect return codes
        • 7.5.1.4.2.5. Binding to unset optional member causes some operations on parent DynamicData object to fail
      • 7.5.1.4.3. Discovery does not complete, and there is no error
      • 7.5.1.4.4. Crash when deserialized_type_object_dynamic_allocation_threshold set to 0
      • 7.5.1.4.5. Wrong return code for DDS::DataWriter::get_matched_subscription_data and DDS::DataReader::get_matched_publication_data
      • 7.5.1.4.6. DataReader reports incorrect sample lost and rejected when receiving coherent set
      • 7.5.1.4.7. QoS policies not resolved to correct values
  • 7.5.2. RTI Security Plugins
    • 7.5.2.1. Fixed in 6.0.1
      • 7.5.2.1.1. Possible lack of SUBSCRIPTION_MATCHED_STATUS if a DataWriter loses liveliness with the DataReader
      • 7.5.2.1.2. Applications directly calling OpenSSL APIs after DomainParticipant deletion may crash
      • 7.5.2.1.3. DataWriter does not report PUBLICATION_MATCHED_STATUS for DataReaders that are inactive when it receives their key material
  • 7.5.3. RTI Code Generator
    • 7.5.3.1. Fixed in 6.1.1
      • 7.5.3.1.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
      • 7.5.3.1.2. Invalid key deserialization for mutable derived types with key members
      • 7.5.3.1.3. Malformed samples with invalid strings not dropped by DataReader in C, traditional C++, and modern C++
    • 7.5.3.2. Fixed in 6.0.1
      • 7.5.3.2.1. Invalid serialization of samples with types containing primitive members that require padding
      • 7.5.3.2.2. Java exception during serialization/deserialization of keyed types whose key is an unkeyed nested type with unbounded members
      • 7.5.3.2.3. Incorrect deserialization in .Net of samples from certain types when published from a writer with disable_inline_keyhash set to true
      • 7.5.3.2.4. Generated code in traditional C++ with namespaces for an IDL containing a nested module called “rti” will not compile
  • 7.5.4. RTI Routing Service
    • 7.5.4.1. Fixed in 6.1.1
      • 7.5.4.1.1. Unbounded memory growth when restarting Service or creating/deleting DomainRoutes
    • 7.5.4.2. Fixed in 6.1.0
      • 7.5.4.2.1. Create method in Service API fails to parse XML snippets that start with ‘str://’
    • 7.5.4.3. Fixed in 6.0.1
      • 7.5.4.3.1. Executable ignores logging QoS
  • 7.5.5. RTI Recording Service
    • 7.5.5.1. Fixed in 6.0.1
      • 7.5.5.1.1. Legacy deserialized database table cannot be replayed or converted if it contains compact byte sequences or arrays
      • 7.5.5.1.2. Segmentation fault in Replay Service or Converter if recorded topics have “::” in their names
  • 7.5.6. RTI Cloud Discovery Service
    • 7.5.6.1. Fixed in 6.0.1
      • 7.5.6.1.1. Cloud Discovery Service executable did not log build ID for DDS libraries