5. What’s Fixed in 7.4.0

This section describes bugs fixed in Connext 7.4.0. These are fixes since 7.3.0 LTS.

Connext 7.4.0 is an early access release. See the Connext Releases page on the RTI website for more information on RTI’s software release model.

[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.

• 5.1. Discovery
  • 5.1.1. [Critical] DNS Tracking not supported with participants using SPDP2
• 5.2. Serialization and Deserialization
  • 5.2.1. [Major] Samples containing sequences using discontiguous buffers failed to be serialized
  • 5.2.2. [Major] Calculated maximum size incorrect for unions with nested unions whose members were empty structures
• 5.3. Usability
  • 5.3.1. [Major] MultiChannel did not work for synchronous DataWriters with large data in best-effort communications
• 5.4. Transports
  • 5.4.1. [Major] Potential high CPU usage if network stack was deleted
  • 5.4.2. [Minor] Wrong configuration of transport_priority QoS on TCP Transport
• 5.5. Reliability Protocol and Wire Representation
  • 5.5.1. [Critical] Repair sample was not sent if the sample was smaller than either transport’s message_size_max
  • 5.5.2. [Critical] Late-joiner DataReader may have stopped receiving samples from DataWriters using a finite durability.writer_depth
  • 5.5.3. [Major] inactivate_nonprogressing_readers did not always inactivate non-progressing readers
  • 5.5.4. [Major] Reliable large data performance issues due to redundant fragment repairs
  • 5.5.5. [Major] DataWriters with finite durability.writer_depth may have sent repairs over unicast instead of multicast
• 5.6. Bandwidth Sensitivity
  • 5.6.1. [Minor] Excessive bandwidth consumption with SPDP2 for peers that were added multiple times
• 5.7. Debuggability
  • 5.7.1. [Minor] Receiving large sequence numbers caused DataReader to incorrectly report on_sample_lost() with a negative total_count
• 5.8. Content Filters and Query Conditions
  • 5.8.1. [Critical] Failure filtering samples on a DataReader when using DynamicData and Zero Copy
• 5.9. TopicQueries
  • 5.9.1. [Major] Response to snapshot TopicQuery may have missed samples for instances that passed the TopicQuery filter
• 5.10. Request-Reply and Remote Procedure Calls
  • 5.10.1. [Major] Python RPC API didn’t support str arguments
• 5.11. Logging
  • 5.11.1. [Trivial] Error messages printed if reader responded to heartbeat from remote writer that was partially removed
  • 5.11.2. [Trivial] Failure getting the Logger instance during instance creation overwrote the verbosity levels of all logging categories to random levels
• 5.12. Dynamic Data
  • 5.12.1. [Major] Incorrect DynamicData behavior involving empty structures
  • 5.12.2. [Major] DynamicData to and from JSON conversion did not include union discriminators
  • 5.12.3. [Minor] DynamicData::get_member_info API returned incorrect member_id in some cases
• 5.13. APIs (Modern C++ API)
  • 5.13.1. [Major] Possible exception thrown due to incorrect DynamicData move constructor or assignment operator
  • 5.13.2. [Major] Modern C++ API was not enabled for x64Vx7SR0630llvm8.0.0.2_rtp
  • 5.13.3. [Minor] find_member_by_id returned INVALID_INDEX in some cases
  • 5.13.4. [Trivial] SampleProcessor not included by rti/rti.hpp header
• 5.14. APIs (Java)
  • 5.14.1. [Major] Unnecessary memory operations when receiving bounded sequences
• 5.15. APIs (Python)
  • 5.15.1. [Major] Exception when printing or converting a sequence of octets to string
  • 5.15.2. [Major] Incorrect deserialization of nested union with unknown discriminator
  • 5.15.3. [Major] x64Linux Connext Python API not able to use libraries from $NDDSHOME/lib
  • 5.15.4. [Minor] QosProvider could not be directly created with QosProviderParams
• 5.16. APIs (Multiple Languages)
  • 5.16.1. [Major] DynamicData Errors when operating on unions with unknown discriminator values
  • 5.16.2. [Minor] Creating a DomainParticipant with a negative domain ID was incorrectly allowed
• 5.17. XML Configuration
  • 5.17.1. [Major] Could not use multiple <types> tags to create user data types
  • 5.17.2. [Minor] Duplicate type names were allowed in an XML file for defining user data types
  • 5.17.3. [Trivial] DDS-prefixed enumerations caused confusion in XSD files
• 5.18. Crashes
  • 5.18.1. [Critical] Potential crash when creating new GuardCondition when low on resources
  • 5.18.2. [Critical] Parsing an XML file with a root “types” tag that contained a “name” attribute led to a segmentation fault
  • 5.18.3. [Critical] Parsing of malformed RTPS packages may have led to bus error in some platforms
  • 5.18.4. [Critical] Potential race conditions in construction or deletion of Requesters and Repliers (C, Traditional C++, C#, and Python)
  • 5.18.5. [Critical] Possible crash when creating dds.DynamicData.Topic with a listener
  • 5.18.6. [Critical] Possible crash after a failure to create Monitoring Library 2.0 object
  • 5.18.7. [Critical] Possible segmentation fault while enabling a DataWriter that enables batching
  • 5.18.8. [Critical] Segmentation fault when copying invalid samples and using Zero Copy transfer over shared memory transport
  • 5.18.9. [Critical] Possible crash when calling DDS_DataWriter_get_matched_subscriptions() or DDS_DataReader_get_matched_publications() on architectures with a weak memory model
  • 5.18.10. [Critical] Possible crash when using QosProvider to load XML file with syntax file:/// on Windows systems
  • 5.18.11. [Critical] Crash on DDS_DomainParticipantFactory_finalize_instance() when using XML-Based Application Creation
  • 5.18.12. [Critical] Parsing of malformed RTPS packets may have led to bus error on some platforms
  • 5.18.13. [Critical] Crash if element in initial_peers longer than 72 characters added
  • 5.18.14. [Major] Potential crash upon serialization, deserialization, or program shutdown when running out of memory
  • 5.18.15. [Major] Possible crash when closing a logger device while it was being used
  • 5.18.16. [Major] Crash during custom transport load when running out of memory
  • 5.18.17. [Major] Precondition failure or segmentation fault when nonBasicTypeName is the name of a module
• 5.19. Hangs
  • 5.19.1. [Critical] String built-in type unregister_type API blocked associated DomainParticipant
  • 5.19.2. [Critical] Potential deadlock when using SHMEM transport on Linux, macOS, and LynxOS systems and killing one application
  • 5.19.3. [Critical] Potential deadlock when creating entities in parallel that use Zero Copy transfer over shared memory transport
  • 5.19.4. [Major] Running out of memory during DomainParticipant creation caused DomainParticipantFactory finalization to hang
• 5.20. Memory Leaks/Growth
  • 5.20.1. [Critical] Parsing XML configuration with large tokens caused uncontrolled resource consumption
  • 5.20.2. [Critical] Potential unbounded memory growth when using DNS tracking
  • 5.20.3. [Critical] Parsing DTD with many nested/recursive entities could cause uncontrolled resource consumption
  • 5.20.4. [Major] Memory leak when parsing malformed XML defined types
  • 5.20.5. [Minor] Possible memory leak when initializing and finalizing the DomainParticipantFactory concurrently
  • 5.20.6. [Minor] Memory leak when parsing XML QoS profile with unknown base_name
  • 5.20.7. [Minor] Memory leak during DomainParticipant creation when running out of memory trying to create the event thread
• 5.21. Data Corruption
  • 5.21.1. [Major] Parsing of malformed DATA_FRAG submessage may have led to unexpected application behavior
• 5.22. OMG Specification Compliance
  • 5.22.1. [Major] Not possible to specify how to deserialize a sample with a discriminator that does not select a member or an unknown enum
• 5.23. Interoperability
  • 5.23.1. [Critical] Incorrect handling of RTPS messages with submessages from different participants
  • 5.23.2. [Critical] RTPS checksums incorrect for multiple RTPS messages received in a single datagram
• 5.24. Vulnerabilities
  • 5.24.1. [Critical] Stack buffer write overflow while parsing malicious license file
  • 5.24.2. [Critical] Stack buffer write overflow while parsing malicious XML types document
  • 5.24.3. [Critical] Stack buffer write overflow while parsing a malicious XML types document
• 5.25. Other
  • 5.25.1. [Critical] Data races on architectures with weak memory model
  • 5.25.2. [Major] Missing implementation of RTI_DL_DistLogger_get_version(), RTI_DL_DistLogger_get_api_build_version(), and RTI_DL_DistLogger_get_api_version_string()
  • 5.25.3. [Major] Incorrect update of DataWriter’s pushed_fragment_count protocol statistic under some conditions
  • 5.25.4. [Minor] IDL annotations printed after typdef specifier