5.4. What’s Fixed in 7.5.0

This section describes bugs fixed in Connext 7.5.0. These are fixes since 7.4.0, described in Previous Releases.

Connext 7.5.0 is an early access release. See the Connext Versions and Lifecycle page for more information on RTI’s software release model.

For what’s new and fixed in other products in the Connext suite, see those products’ release notes on the RTI Community Portal or in your installation.

[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.4.1. Discovery
  • 5.4.1.1. [Critical] Undefined behavior when serializing using any of the builtin discovery plugins
  • 5.4.1.2. [Critical] Incorrect locators used on newly created DataWriters or DataReaders after a Locator Reachability event
  • 5.4.1.3. [Major] DomainParticipants using SPDP2 and fragmentation of the participant configuration messages failed to complete discovery
  • 5.4.1.4. [Major] DomainParticipants failed to announce that endpoint was not reachable when internal clock was monotonic and external clock was real-time
  • 5.4.1.5. [Minor] DomainParticipants using LBED unregistered remote DataWriters when a remote participant was deleted instead of deleting them
• 5.4.2. Usability
  • 5.4.2.1. [Minor] Unnecessary QoS consistency checks for best effort DataWriters
• 5.4.3. Transports
  • 5.4.3.1. [Critical] Shared Memory communications might not have been recovered if a DataReader crashed or was ungracefully killed
• 5.4.4. Reliability Protocol and Wire Representation
  • 5.4.4.1. [Critical] Writer-side filtered samples not always marked as acknowledged when application acknowledgment was used
• 5.4.5. Performance and Scalability
  • 5.4.5.1. [Critical] High CPU usage and delayed events in a DataReader managing many instances of a deleted DataWriter
• 5.4.6. Debuggability
  • 5.4.6.1. [Major] Incorrect source port for some Real-Time WAN Transport packets recorded with network capture
  • 5.4.6.2. [Trivial] RTI DDS Spy showed unprintable character in help output
• 5.4.7. Content Filters and Query Conditions
  • 5.4.7.1. [Minor] Setting parameters on QueryCondition could have led to slightly inefficient refiltering
• 5.4.8. Request-Reply and Remote Procedure Calls
  • 5.4.8.1. [Minor] Request-reply and RPC readers created without explicitly loading BuiltinQosLib::Pattern.RPC did not set reliability.max_blocking_time to 10 seconds
• 5.4.9. Logging
  • 5.4.9.1. [Trivial] Incorrect informational log messages when adding or removing remote writers in local readers
• 5.4.10. APIs (C or Traditional C++)
  • 5.4.10.1. [Minor] Incorrect return code for DomainParticipant::assert_liveliness API on disabled participant
• 5.4.11. APIs (Java)
  • 5.4.11.1. [Major] Unnecessary memory operations when receiving inherited bounded sequences
  • 5.4.11.2. [Major] For types with strings, sample size calculation in Java may have overestimated serialized size
• 5.4.12. APIs (C# API)
  • 5.4.12.1. [Trivial] .NET bundle information not displayed in Launcher
• 5.4.13. APIs (Python)
  • 5.4.13.1. [Critical] Incompatibility between Python API and other APIs when using int8 type
  • 5.4.13.2. [Major] Python API didn’t support reading TopicQuery samples exclusively
  • 5.4.13.3. [Minor] Python API didn’t provide enumeration to set Real-Time WAN Transport in code
• 5.4.14. APIs (Multiple Languages)
  • 5.4.14.1. [Minor] Some properties no longer accepted LENGTH_UNLIMITED string as a valid value
  • 5.4.14.2. [Minor] Request-reply and RPC may have used standard PID instead of selected one
• 5.4.15. XML Configuration
  • 5.4.15.1. [Minor] Possible failure when loading an XML file containing a long comment
• 5.4.16. Instances
  • 5.4.16.1. [Major] Failure to register instances of mutable flat data types
• 5.4.17. Crashes
  • 5.4.17.1. [Critical] Stack smashing error when serializing strings with RTI_CDR_SIZEOF_LONG_DOUBLE set to 16 in C++11 in release mode using GCC compiler
  • 5.4.17.2. [Critical] Possible crash on MIGInterpreter_parse while receiving data at the same time that entities are removed, on architectures with a weak memory model
  • 5.4.17.3. [Critical] Race condition in RTI Monitoring Library 2.0 caused a crash
  • 5.4.17.4. [Critical] Segmentation fault if Application Kind contained more than 255 characters when calling RTI_DL_DistLogger_getInstance
  • 5.4.17.5. [Critical] Potential crash if creation of Publisher or Subscriber failed while database garbage collection process was running
  • 5.4.17.6. [Critical] Possible crash when calling any write operation on architectures with a weak memory model
  • 5.4.17.7. [Critical] Stack overflow when parsing very long SQL filter expressions
  • 5.4.17.8. [Critical] Possible crash when creating DomainParticipants concurrently
  • 5.4.17.9. [Critical] Crash when writing data on a ContentFilteredTopic in combination with transient durability and delegated reliability
  • 5.4.17.10. [Major] Possible crash after memory allocation failures
  • 5.4.17.11. [Major] Using unbounded or very large types with query conditions in Python API could cause crash
  • 5.4.17.12. [Major] Segmentation fault if application ran out of memory while generating a log message
• 5.4.18. Hangs
  • 5.4.18.1. [Critical] Potential deadlock when using TCP Transport on Windows systems if WINDOWS_WAITFORMULTIPLEOBJECTS was selected as the socket monitoring API
  • 5.4.18.2. [Major] Potential deadlock when using Durable Writer History if there was a failure while creating the connection
  • 5.4.18.3. [Major] Potential deadlock when using DynamicData in Debug libraries if TypePlugin initialization failed
  • 5.4.18.4. [Major] Potential issues using rti.asyncio.run or asyncio.run with dds.DataReader.take_async
  • 5.4.18.5. [Major] RPC failures when serializing the return value or out/inout parameters caused a timeout on client side
• 5.4.19. Memory Leaks/Growth
  • 5.4.19.1. [Critical] Possible unbounded memory growth on DataReader of keyed type after failing to match with a remote DataWriter
  • 5.4.19.2. [Critical] Memory leaks and errors when using DynamicDataReaders or FlatData DataReaders plus DDS-fragmentation and compression or encryption
  • 5.4.19.3. [Critical] Unbounded memory growth when using DynamicDataReaders with multiple data representations and keyed types
  • 5.4.19.4. [Critical] Unbounded memory growth when using RECOVER instance state consistency and instances were removed from DataReader queue
  • 5.4.19.5. [Major] Memory leak when parsing invalid module in XML
  • 5.4.19.6. [Major] Memory leak when using DynamicData with types containing optional members of string aliases or when cloning such types
  • 5.4.19.7. [Minor] DynamicDataTypeSupport objects not reclaimed by garbage collector
  • 5.4.19.8. [Minor] Potential DynamicData sample leaked on DataReader deletion
• 5.4.20. Data Corruption
  • 5.4.20.1. [Critical] Potential corruption in samples with sequences of strings when using Traditional C++ API and std::string
  • 5.4.20.2. [Critical] Rare race condition may have led to undefined behavior
  • 5.4.20.3. [Major] Possible data corruption when using ISerializer<T> to serialize a sample
• 5.4.21. Entities
  • 5.4.21.1. [Major] Error when setting QoS on Publisher or Subscriber without endpoints
• 5.4.22. Interoperability
  • 5.4.22.1. [Critical] XCDR serialization of a mutable union with a discriminator value that does not select a union member was not compliant with OMG specification
  • 5.4.22.2. [Critical] RTPS messages containing vendor-specific submessages could have been dropped
  • 5.4.22.3. [Critical] Multiple RTPS messages received in a single datagram caused issues
• 5.4.23. Vulnerabilities
  • 5.4.23.1. [Critical] Potential stack buffer overflow in Connext applications when parsing an XML type
  • 5.4.23.2. [Critical] Potential stack buffer write overflow in license-managed Core Libraries when setting RTI_LICENSE_FILE environment variable
  • 5.4.23.3. [Critical] Buffer write overflow while parsing malicious license file
  • 5.4.23.4. [Critical] Potential integer overflow in Connext applications on 32-bit systems when parsing XML files with very large number of default attributes or levels of nesting
• 5.4.24. Other
  • 5.4.24.1. [Critical] Data races on architectures with weak memory models
  • 5.4.24.2. [Major] Printing an IDL union with an enum discriminator could have produced an incorrect output
  • 5.4.24.3. [Major] Incorrect CPU assignment when using THREAD_SETTINGS_CPU_RR_ROTATION in receiver_pool
  • 5.4.24.4. [Trivial] Possible data race when creating DomainParticipants
  • 5.4.24.5. [Trivial] Printing a type with an annotation using an enum produced an incorrect output