6.2. What’s Fixed in 7.2.0
This section describes bugs fixed in Connext 7.2.0. These are fixes since 7.1.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.2.1. Discovery
- 6.2.1.1. [Critical] SPDP2 participants may not have completed discovery if IP mobility event occurred during discovery *
- 6.2.1.2. [Critical] Crash if initial_peers sequence contained a NULL string
- 6.2.1.3. [Critical] Unbounded memory growth when creating/deleting DomainParticipants *
- 6.2.1.4. [Major] Failure to deserialize participant discovery information incorrectly allowed discovery to complete
- 6.2.2. Serialization and Deserialization
- 6.2.2.1. [Critical] Unbounded memory growth when deserializing SPDP discovery sample
- 6.2.2.2. [Critical] Potential unexpected behavior or crash when deserializing SPDP discovery sample
- 6.2.2.3. [Trivial] Wrong error message when deserializing PropertyQos property value and exceeding property_string_max_length resource limit
- 6.2.3. Debuggability
- 6.2.4. Transports
- 6.2.4.1. [Critical] Ungracefully terminated QNX processes using SHMEM transport prevented startup of new processes due to unclosed POSIX semaphores
- 6.2.4.2. [Critical] Stalled communication when using shared-memory transport
- 6.2.4.3. [Major] Connext started before Windows completed duplicate address detection on network interfaces
- 6.2.4.4. [Minor] QNX applications using shared-memory transport may have led to thread priority inversion issues
- 6.2.4.5. [Minor] Overflow in default TransportMulticastMappingQosPolicy procedure
- 6.2.5. Reliability Protocol and Wire Representation
- 6.2.6. Content Filters and Query Conditions
- 6.2.7. Dynamic Data
- 6.2.8. Performance and Scalability
- 6.2.9. APIs (C or Traditional C++)
- 6.2.10. APIs (Modern C++ API)
- 6.2.10.1. [Critical] Unexpected rti.connextdds.PreconditionNotMetError when setting optional string members in QoS policies
- 6.2.10.2. [Critical] Move constructors for some of the built-in topic-types were incorrectly implemented
- 6.2.10.3. [Critical] Manually closing some built-in readers could lead to a crash
- 6.2.10.4. [Critical] Incorrect implementation of DynamicDataMemberInfo constructor and assignment may have led to undefined behavior
- 6.2.10.5. [Major] int8_t, uint64_t, int64_t not supported as primitive types in Dynamic Type API
- 6.2.10.6. [Major] Policy getter for rti::core::policy::Monitoring previously missing *
- 6.2.11. APIs (Java)
- 6.2.12. APIs (Python)
- 6.2.13. APIs (Multiple Languages)
- 6.2.14. XML Configuration
- 6.2.14.1. [Major] Creating Topic-specific entities from a <qos_profile> using QoS profile inheritance and/or composition returned incorrect values
- 6.2.14.2. [Major] Using languageBinding attribute on union types in XML caused parsing error
- 6.2.14.3. [Minor] configuration_variables tag was not effective
- 6.2.14.4. [Minor] Incorrect parsing of data_representation attribute in XML type definitions
- 6.2.15. Instances
- 6.2.16. Crashes
- 6.2.16.1. [Critical] Race condition when using multiple threads to enable same DomainParticipant
- 6.2.16.2. [Critical] Possible crash gathering periodic metrics for a resource that was being added or deleted at the same time *
- 6.2.16.3. [Critical] Potential crash when configuring logging verbosity to NDDS_CONFIG_LOG_VERBOSITY_STATUS_LOCAL or higher
- 6.2.16.4. [Critical] Malloc called when handling SIGSEGV
- 6.2.16.5. [Critical] Calling delete_contained_entities APIs could cause a crash in the thread that collects periodic metrics *
- 6.2.16.6. [Critical] Application could crash when disabling and re-enabling Monitoring Library 2.0 due to internal error *
- 6.2.16.7. [Critical] Low-memory conditions could lead to crash on several platforms if allocation of high resolution clock failed
- 6.2.17. Entities
- 6.2.17.1. [Critical] Application may have hung when deleting a monitored DDS entity *
- 6.2.17.2. [Major] Monitoring Library 2.0 incorrectly collected both enabled and disabled DDS Entities *
- 6.2.17.3. [Major] Monitoring Library 2.0 did not assert disabled DDS Entities when the Entities were enabled *
- 6.2.18. Interoperability
- 6.2.19. Vulnerabilities
- 6.2.19.1. [Critical] Out-of-bounds read while deserializing malformed partition parameters from malicious RTPS message *
- 6.2.19.2. [Critical] Out-of-bounds read while deserializing malformed IPv6 locator from malicious RTPS message
- 6.2.19.3. [Critical] Remote modification of DomainParticipant names in unsecure system
- 6.2.20. Other
- 6.2.20.1. [Critical] Possible hang in application if something failed while adding a new observable resource *
- 6.2.20.2. [Critical] Application may have hung when event and event snapshot were published simultaneously for same observable resource *
- 6.2.20.3. [Critical] Unable to start Launcher, Admin Console, Code Generator, and Monitor in Windows when the RTI Workspace contained white spaces *
- 6.2.20.4. [Critical] Deadlock issue resolved when disabling Monitoring Library 2.0 during command processing *
- 6.2.20.5. [Major] Native Android applications were not shipped
- 6.2.20.6. [Major] References to missing header file in Connext Professional source bundle
- 6.2.20.7. [Major] Access to an internal field of observable resources was not thread safe *
- 6.2.20.8. [Minor] Running rtisetenv_<arch>.bat caused issues in PATH environment *
- 6.2.20.9. [Minor] Error creating a DataWriter using durable writer history if setting property dds.data_writer.history.odbc_plugin.builtin.sample_cache_max_size to -1
- 6.2.20.10. [Trivial] Connext did not print array dimensions for aliases that were arrays
* This bug does not affect you if you are upgrading from 6.1.x or earlier.