6.4. What’s Fixed in 7.1.0

This section describes bugs fixed in Connext 7.1.0. These are fixes since 7.0.0.

[Critical]: System-stopping issue, such as a crash or data loss.
[Major]: Significant issue with no easy workaround.
[Minor]: Issue that usually has a workaround.
[Trivial]: Small issue, such as a typo in a log.

• 6.4.1. Fixes Related to Discovery
  • 6.4.1.1. [Critical] Unbounded memory growth when using domain tags or DomainParticipant partitions
  • 6.4.1.2. [Critical] Most up-to-date participant configuration may not have been received by other participants and may have led to discovery not completing
  • 6.4.1.3. [Major] Error deleting remote endpoints with specific GUID prefixes using debug libraries
  • 6.4.1.4. [Major] Participant failed to assert remote participant if usability of shared memory transport changed *
  • 6.4.1.5. [Major] Unexpected warning during discovery when multicast disabled
  • 6.4.1.6. [Minor] Potential memory leak when creation of any of the built-in discovery plugins failed
  • 6.4.1.7. [Minor] Unexpected, invalid locator propagated within builtin topics
• 6.4.2. Fixes Related to Serialization and Deserialization
  • 6.4.2.1. [Critical] Unexpected union value when receiving a discriminator that does not select any union member on DataReader’s type
  • 6.4.2.2. [Critical] Serialization of samples failed or produced a segmentation fault for types with max serialized size larger than 2GB
  • 6.4.2.3. [Critical] Potential sample corruption when deserializing a malformed RTPS message
  • 6.4.2.4. [Critical] Unbounded memory growth when deserializing a malformed RTPS message
• 6.4.3. Fixes Related to Debuggability
  • 6.4.3.1. [Critical] Hang/crash when invoking a DataReader/DataWriter discovery snapshot within a callback function *
  • 6.4.3.2. [Major] Unexpected fatal error when number of instances reached the limit *
  • 6.4.3.3. [Trivial] Memory leak if network capture initialization failed
  • 6.4.3.4. [Trivial] Unexpected log messages at warning verbosity
• 6.4.4. Fixes Related to Transports
  • 6.4.4.1. [Critical] Possible data loss after a Connext application lost its multicast interfaces or gained its first multicast interface
  • 6.4.4.2. [Major] DomainParticipant with non-default metatraffic_transport_priority QoS did not complete discovery
  • 6.4.4.3. [Major] TCP Transport did not run with Windows debug libraries when socket_monitoring_kind was set to IOCP *
  • 6.4.4.4. [Minor] dds.transport.minimum_compatibility_version property did not properly adjust locator format
• 6.4.5. Fixes Related to Reliability Protocol and Wire Representation
  • 6.4.5.1. [Critical] Samples not delivered to Required Subscription DataReaders when DataWriter used durable writer history and DataReaders disabled positive ACKs
  • 6.4.5.2. [Critical] DataReader may not have received samples that were sent as gapped samples to another DataReader over multicast
  • 6.4.5.3. [Critical] Unexpected precondition error with debug libraries on a reliable DataWriter while sending a GAP
  • 6.4.5.4. [Minor] DDS fragmentation may have led to more fragments than expected for a sample *
• 6.4.6. Fixes Related to Content Filters and Query Conditions
  • 6.4.6.1. [Critical] Unexpected “RTIXCdrSampleInterpreter_initializeSampleWInstruction” error log messages when using QueryConditions, ContentFilteredTopics, TopicQueries, or Multi-Channel
• 6.4.7. Fixes Related to Dynamic Data
  • 6.4.7.1. [Major] DynamicData DataWriters incorrectly serialized optional empty sequences as null
• 6.4.8. Fixes Related to APIs
  • 6.4.8.1. [Minor] DynamicData method to get member type missing in Modern C++ and C# APIs
  • 6.4.8.2. Fixes Related to Modern C++ API
    • 6.4.8.2.1. [Major] banish and subject_name APIs were unresolved in Modern C++ Windows dynamic libraries *
    • 6.4.8.2.2. [Major] Unnecessary small memory allocation in some operations, including read/take
    • 6.4.8.2.3. [Major] close() operation of a ContentFilteredTopic created from XML didn’t work
  • 6.4.8.3. Fixes Related to C# API
    • 6.4.8.3.1. [Critical] Exception when disposing a DomainParticipant or when entities were not properly disposed
    • 6.4.8.3.2. [Major] Windows library dependency missing from .NET API NuGet packages *
  • 6.4.8.4. Fixes Related to Java API
    • 6.4.8.4.1. [Critical] Java API leaked some objects in certain DomainParticipantFactory operations
    • 6.4.8.4.2. [Major] get_typecode method of a DomainParticipant in Java API failed when the type contained a wstring element
  • 6.4.8.5. Fixes Related to Python API
    • 6.4.8.5.1. [Critical] Possible deadlock between creation of a dds.Topic and a listener callback
    • 6.4.8.5.2. [Major] DynamicData accessor for an enum member in a base type failed (Python API)
    • 6.4.8.5.3. [Major] Possible incorrect default values when receiving extensible data
    • 6.4.8.5.4. [Major] Some APIs where missing, incorrectly named, or have been deleted
    • 6.4.8.5.5. [Major] Listeners may not have been called in some situations
• 6.4.9. Fixes Related to XML Configuration
  • 6.4.9.1. [Critical] Memory leak after an error parsing XML file with <include> tag
  • 6.4.9.2. [Minor] Failed to parse XML configuration file containing type member with useVector attribute
  • 6.4.9.3. [Minor] XML composition overwrote system information properties with defaults instead of correct values
• 6.4.10. Fixes Related to Request-Reply and RPC
  • 6.4.10.1. [Critical] Exceptions sending result of remote operation may have crashed server application
  • 6.4.10.2. [Critical] RPC: deadlock when Server::close() was called before Server::run()
  • 6.4.10.3. [Critical] Possible unbounded memory growth when creating many Requesters
  • 6.4.10.4. [Critical] Memory leak in Java Request-Reply API
  • 6.4.10.5. [Critical] Possible data race using Sample and WriteSample classes (Traditional C++ API only)
  • 6.4.10.6. [Major] RPC interface evolution did not work
• 6.4.11. Fixes Related to Shipped Examples
  • 6.4.11.1. [Minor] Hello World TCP example always linked TCP Transport library dynamically
• 6.4.12. Fixes Related to Vulnerabilities
  • 6.4.12.1. [Critical] Arbitrary read access while parsing malicious RTPS message *
    • 6.4.12.1.1. User Impact without Security
    • 6.4.12.1.2. User Impact with Security
  • 6.4.12.2. [Critical] Out-of-bounds read while parsing malicious RTPS message
    • 6.4.12.2.1. User Impact without Security
    • 6.4.12.2.2. User Impact with Security
  • 6.4.12.3. [Critical] Out-of-bounds write while parsing malicious RTPS message
    • 6.4.12.3.1. User Impact without Security
    • 6.4.12.3.2. User Impact with Security
  • 6.4.12.4. [Critical] Buffer overflow in shared memory if memory was tampered
    • 6.4.12.4.1. User Impact without Security
    • 6.4.12.4.2. User Impact with Security
  • 6.4.12.5. [Critical] Out-of-bounds read while uncompressing malformed data from malicious RTPS message
    • 6.4.12.5.1. User Impact without Security
    • 6.4.12.5.2. User Impact with Security
• 6.4.13. Fixes Related to Crashes
  • 6.4.13.1. [Critical] Rare segmentation fault when deleting DomainParticipant or Publisher containing DataWriters using durable writer history
  • 6.4.13.2. [Critical] Segmentation fault when creation of DomainParticipant failed due to lack of resources
  • 6.4.13.3. [Critical] Potential hang upon SIGSEGV signal from a Connext application
  • 6.4.13.4. [Critical] Creating DynamicDataTypePlugin with TypeCode from discovery and using content filtering caused segmentation fault
  • 6.4.13.5. [Critical] Application crash when calling DDS_DataReader_take_discovery_snapshot on a DataReader with a ContentFilteredTopic *
  • 6.4.13.6. [Critical] Crash with NULL listeners and non-none status masks in C applications that mixed types with and without Zero Copy
  • 6.4.13.7. [Critical] Memory was read after it was freed by deleting a Topic with local logging level enabled
  • 6.4.13.8. [Critical] Possible segmentation fault when disabling loopback interface
  • 6.4.13.9. [Critical] Segmentation fault could occur if creation of DataReader failed
  • 6.4.13.10. [Critical] Potential crash when DomainParticipant deleted after creating DataWriter with automatic liveliness kind
  • 6.4.13.11. [Critical] Possible crash on TCP transport when large number of file descriptors were open
  • 6.4.13.12. [Critical] Application using Monitoring Libraries may have produced segmentation fault during DataReader creation
  • 6.4.13.13. [Critical] Possible segmentation fault when using Monitoring Library
• 6.4.14. Other Fixes
  • 6.4.14.1. [Critical] Broken communication when DataWriter with transport priority discovered DataReader with multicast receive address
  • 6.4.14.2. [Critical] Potential hang upon SIGSEGV signal from a Connext application
  • 6.4.14.3. [Critical] Samples could be lost using group order access or collaborative DataWriters
  • 6.4.14.4. [Critical] Release 6.1.2 was not FACE compliant
  • 6.4.14.5. [Critical] Using dh_param_files leaked memory
  • 6.4.14.6. [Critical] Segmentation fault when mixing build types in applications linked against libraries in “Find Package” Cmake script
  • 6.4.14.7. [Major] Error sending batch when batch size exceeded transport MTU
  • 6.4.14.8. [Major] No more than 100 asynchronous publisher threads could be created
  • 6.4.14.9. [Major] Unexpected precondition error while creating a DomainParticipant with debugging libraries using fast database cleanup period
  • 6.4.14.10. [Major] In FindPackage script, low_bandwidth_edisc imported target library was missing
  • 6.4.14.11. [Minor] Potential memory leak when creation of any of the built-in discovery plugins failed
  • 6.4.14.12. [Minor] Problems visualizing participants using Generic.MinimalMemoryFootprint profile with Admin Console
  • 6.4.14.13. [Minor] Failure to load a string-based private key leaked memory
  • 6.4.14.14. [Minor] CONNEXTDDS_ARCH environment variable in FindPackage script was not picked up correctly
  • 6.4.14.15. [Trivial] Incorrect “Supported platforms” documentation section for FindRTIConnextDDS.cmake

* This bug does not affect you if you are upgrading from 6.1.x or earlier.