6.6. What’s Fixed in 7.0.0

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

[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.6.1. Fixes Related to Callbacks and Waitsets
  • 6.6.1.1. [Critical] Unsafe combinations of masks and Listeners may have led to segmentation fault
  • 6.6.1.2. [Critical] Failure calling DDS_Subscriber::get_datareaders in DDS_SubscriberListener::on_data_on_readers callback implementation
  • 6.6.1.3. [Critical] Using certain callbacks at DomainParticipant or Publisher level may have led to segmentation fault
  • 6.6.1.4. [Major] DDS_SubscriberListener::on_data_on_readers on a participant or subscriber not called when Listener installed after the entity is enabled
  • 6.6.1.5. [Major] Unable to assign callback function for on_sample_removed event using Modern C++ API
• 6.6.2. Fixes Related to Discovery
  • 6.6.2.1. [Critical] Unexpected memory growth when DataReader could not be matched with DataWriter due to unexpected error condition
  • 6.6.2.2. [Critical] Possible crash upon discovery of applications with unreachable locators
  • 6.6.2.3. [Critical] Communication problems with applications using shared memory on INTEGRITY systems
  • 6.6.2.4. [Critical] Unbounded memory growth in Spy when discovering multiple endpoints with the same Topics and types
  • 6.6.2.5. [Major] Types containing Typedefs were sent without the typedefs in discovery when using DynamicData
  • 6.6.2.6. [Major] Unnecessary discovery traffic related to IP mobility events on interfaces irrelevant to the transport
• 6.6.3. Fixes Related to Transports
  • 6.6.3.1. [Critical] Communication problems with applications using shared memory on INTEGRITY systems
  • 6.6.3.2. [Critical] Race condition could cause unbounded memory growth in TCP Transport Plugin
• 6.6.4. Fixes Related to Filtering and TopicQuery
  • 6.6.4.1. [Critical] Connext application using filtering feature may have crashed after running out of memory
  • 6.6.4.2. [Critical] Creation of a ContentFilteredTopic or reception of TopicQuery samples may have taken long time for complex types
  • 6.6.4.3. [Critical] rti::topic::find_registered_content_filters led to infinite recursion
  • 6.6.4.4. [Critical] Incorrect results for Unions when using DynamicData or Content Filters
  • 6.6.4.5. [Major] Unnecessary repair traffic for DataWriters using TopicQueries and asynchronous publishing
  • 6.6.4.6. [Major] Continuous creation of TopicQueries may have led to unnecessary memory fragmentation in OS memory allocator
  • 6.6.4.7. [Major] Samples may have been unnecessarily filtered by Connext DataReader when DataWriter was from different DDS vendor
  • 6.6.4.8. [Minor] Unnecessary sample filtering on a DataReader for samples already filtered by a DataWriter
• 6.6.5. Fixes Related to Group Presentation
  • 6.6.5.1. [Critical] Application may not have received samples of coherent set when using GROUP access scope and TRANSIENT_LOCAL durability
  • 6.6.5.2. [Critical] Segmentation fault when using GROUP_PRESENTATION_QOS or HIGHEST_OFFERED_PRESENTATION_QOS and setting filter_redundant_samples to FALSE on DataReader
  • 6.6.5.3. [Major] Application may stop receiving samples from DataReaders using GROUP_PRESENTATION_QOS
• 6.6.6. Fixes Related to XML Configuration
  • 6.6.6.1. [Major] Parsing error loading XML configuration file containing a const whose expression refers to an enumerator
  • 6.6.6.2. [Major] Parsing error loading an XML configuration file with enum type containing enumerator whose value was an expression
  • 6.6.6.3. [Major] Parsing error loading an XML configuration file with an enum type containing an enumerator whose value was an expression referring to another enumerator
  • 6.6.6.4. [Minor] Discrepancy between range defined by schema and that defined by API
  • 6.6.6.5. [Minor] Parsing error loading XML configuration file with enum type containing enumerator whose value was an expression referring to a const
  • 6.6.6.6. [Minor] Type limits not checked for some attributes of XML types definition
  • 6.6.6.7. [Trivial] Removed some elements in the XSD that were not supported internally but could be defined in XML
  • 6.6.6.8. [Trivial] Builtin Discovery Plugins was not treated as a mask by the XSD file
• 6.6.7. Fixes Related to Vulnerabilities
  • 6.6.7.1. Fixes related to Connext
  • 6.6.7.2. Fixes related to third-party dependencies
• 6.6.8. Fixes Related to APIs
  • 6.6.8.1. [Major] Copy of SampleInfo::coherent_set_info field was not supported
  • 6.6.8.2. [Major] Corruption of LoanedDynamicData object when moved in some situations (Modern C++ API only)
  • 6.6.8.3. [Major] Calling DynamicData::set_complex_member with an aliased type failed
  • 6.6.8.4. [Major] Possible wrong results when adding Time or Duration objects that used very large numbers
  • 6.6.8.5. [Major] Java API did not support RtpsReliableReaderProtocol_t.receive_window_size
  • 6.6.8.6. [Minor] Input parameters to Property and DataTag helper functions do not have “const”
  • 6.6.8.7. [Minor] Standard 64-bit integer types are now supported (Modern C++ API)
  • 6.6.8.8. [Minor] Assigning DataWriter and DataReaderQos from a TopicQos caused a build error
  • 6.6.8.9. [Minor] In XML-based applications, generated IDL types did not take precedence over XML DynamicTypes (C# API)
  • 6.6.8.10. [Minor] Namespaces ignored when a type was explicitly registered in C# for XML-based applications
• 6.6.9. Fixes Related to Crashes
  • 6.6.9.1. [Critical] DataReader C++ application crashed if it received tampered sample with unsupported encapsulation ID
  • 6.6.9.2. [Critical] Segmentation fault after calling DomainParticipant::register_durable_subscription with a group containing a long role_name
  • 6.6.9.3. [Critical] Segmentation fault when application using MultiChannel ran out of memory
  • 6.6.9.4. [Critical] Application crashed when capturing traffic for a DomainParticipant created before enabling network capture
  • 6.6.9.5. [Critical] Possible crash when writing a sample
  • 6.6.9.6. [Critical] Potential crash during type registration if system ran out of memory
  • 6.6.9.7. [Critical] Segmentation fault after calling DomainParticipant::delete_durable_subscription with a group containing a long role_name
  • 6.6.9.8. [Critical] Potential crash or memory corruption if user application using thread-specific storage
  • 6.6.9.9. [Minor] Simultaneous deletion of an entity by multiple threads caused a crash when using Java
• 6.6.10. Other Fixes
  • 6.6.10.1. [Critical] Serialization/deserialization of non-primitive sequences and arrays for XCDR2_DATA_REPRESENTATION did not follow Extensible Types specification
  • 6.6.10.2. [Critical] Possible hang when using best-effort writers and asynchronous publishing
  • 6.6.10.3. [Critical] Runtime error when using debug libraries for QNX x86 platform
  • 6.6.10.4. [Critical] Pushed samples may not have been received by reliable DataReader when DataWriter published Type that supports Zero Copy transfer over shared memory
  • 6.6.10.5. [Critical] Potential truncation of application-level acknowledgment response data
  • 6.6.10.6. [Critical] Potential Valgrind invalid read when logging a message or enabling heap monitoring
  • 6.6.10.7. [Major] Various issues with RtpsReliableWriterProtocol_t::nack_suppression_duration
  • 6.6.10.8. [Major] Possible error message printed during Entity disposal
  • 6.6.10.9. [Major] Source IP on Spy was not correct when DataWriters with same Topic were on different machines
  • 6.6.10.10. [Minor] Unbounded memory growth in Monitoring Library when creating and deleting endpoints
  • 6.6.10.11. [Minor] Unexpected behavior when two threads crashed at the same time on Windows systems
  • 6.6.10.12. [Minor] DataReaders setting reader_qos.protocol.expects_inline_qos to TRUE incorrectly matched with DataWriters
  • 6.6.10.13. [Minor] Writer using durable writer history may not have blocked after send window filled up when disable positive ACKs was enabled
  • 6.6.10.14. [Trivial] Error messages displayed that should not have been, when printing DataReaderQoS objects
  • 6.6.10.15. [Trivial] Unnecessary sockets created during initialization of library
  • 6.6.10.16. [Trivial] Malformed IDL printed if multiple labels used for default case of a union